Cyrus 2.1.11 on BSDi 4.3.1

[Echo Online Development Team]

Greetings, I hope I am posting the problem to the right list, if not, please direct me to the appropriate list.   We are having a serious issue with Cyrus on BSDi 4.3.1.  Over time (aprox 24 hours) Cyrus begins to slow down to the point where IMAP clients begin to time out.  Restarting Cyrus fixes the problem for another 24-36 hours.    The one error message we suspect is "DBERROR db4: 475 lockers"   I've been doing some research and found that this error message is normal, however, I have never seen any postings which refer to the number of lockers being so high.    Our software setup is as follows:   Software:   BSDi 4.3.1 Binary Cyrus imap v2.1.11     Two custom patchs to the code -         1) Applied the NetBSD patches to ctl_cyrusdb.c which remove the trailing slash from the backup dir names, as BSDi does not support trailing slashes to the rmdir call         2) Commented out /* limit_fds(RLIM_INFINITY); */ in master.c, as this call returns -1 in BSDi.  Commenting it out means that Cyrus should default to the OS max.   Cyrus SASL 2.1.10   db-4.1.25 (With one patch listed on the sleepycat website)   Can any one provide any insight or steps we can take to debug this setup?  If any of the Cyrus developers need access to a BSDi box, we are more than willing to provide a development BSDi 4.3.1 machine.   Thanks in advance,   M. Gamble Echo Online Administration