Aleksandar Milivojevic wrote:
Quoting Scott Russell <[EMAIL PROTECTED]>:
Can anyone comment on how the cyrus-imapd 2.3.3-1 RPM is working for
them? I remember there were some stability problems in imapd after
2.3.1-3 which was tracking CVS bug fixes and it was recommended to
back down to 2.3.1-2. I'm not sure what became of those reports or if
they have resurfaced again under 2.3.3-1.
I had it installed on couple of testing boxes. It worked OK for
"single-server" installation. However, cluster (Murder) type of
installation was unusable. The mupdate process would just suck CPU and
get stuck eventually. I've wrote about this problem on the list, and it
seems at least one more person hit the same problem (see the thread with
subject "cyrus murder, mupdate sucking up CPU"). I also opened bugzilla
entry (bug# 2806). I had same problem with all 2.3.x that were released
so far.
I've verified that a problem exists in mupdate due to some code changes
that I made in prot_select(). I haven't fixed it yet, but I'm working
on it (debugging threaded code sucks).
--
Kenneth Murchison
Systems Programmer
Project Cyrus Developer/Maintainer
Carnegie Mellon University
----
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
