RE: Several issues with 2.1.13
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wil Cooley Sent: Tuesday, 10 June 2003 9:23 a.m. To: [EMAIL PROTECTED] Subject: Re: Several issues with 2.1.13 Got it. But John's probably right about the kernel keeping the sockets open. But we never had this problem with cucipop (that's what I always Do you really care about the kernel keeping the sockets open? You *probably* have plenty of them available, user who got disconnected will *probably* get new IP address assigned when he next time dials-in and he'll be able to download his e-mail, at least from the kernel TCP/IP stack perspective, assuming that pop3d is working ok. Or am I missing something here? Best regards, Bojan Zdrnja
RE: effect of changing database backends
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of twk Sent: Wednesday, 28 May 2003 3:25 a.m. To: [EMAIL PROTECTED] Subject: effect of changing database backends Excuse me if these are obvious questionswe are currently dealing with some loading issues and are investigating ways to bring the load down. - On our 2.0.16 Cyrus servers, all the database backends are DB3. What sort of improvement could we see if we convert to the skiplist backend? Should we expedite this change? I had a same problem with database backends. Basically with very high number of requests load went pretty high on box. Check the following message about recommended database formats: http://asg.web.cmu.edu/archive/message.php?mailbox=archive.cyrus-saslmsg=23 11 Best regards, Bojan Zdrnja
