Roy McMorran wrote: > Often throughout the day I see instances where an httpd process will > spike up to 100% cpu utilization and stay there for an extended period > of time. After correlating information from a bunch of log files, I think I've found the circumstances that precipitate this problem. It seems to be a case of one or more users running Roundcube *and* another email program at the same time.
UW-IMAP doesn't want to serve the same inbox to both imap clients. One of them gets cut off at the knees. Eg: Apr 3 14:51:10 mail imapd[12962]: [ID 289526 mail.info] Killed (lost mailbox lock) user=redacted host=mail.example.org [xxx.xxx.xxx.xxx] When the loser is Roundcube we get into the 100% CPU / CLOSE_WAIT scenario I described earlier. Is there any way we can make Roundcube more resilient in this situation? Or is there an IMAP server that isn't quite so brutal? Thanks, Roy -- Roy McMorran Systems Administrator MDI Biological Laboratory [EMAIL PROTECTED] _______________________________________________ List info: http://lists.roundcube.net/dev/
