Massive Problems (lmtp, db corruption) - Ahh!

[Su Li]

It won't limit other processes. I only limited the number of processes for lmtpd. Other processes like imapd can still go 10, 20, 30 or more. 

I agree that unlimited can have a big number. But to be able to config will be very very helpful. The reseason, I change the code is, if there are too many lmtpd is very harmful. Lmptd will fight for db, the db lock will go up, and new lmptd will be created but still can not get db. So the number of lmtpd should be limited to a reseanable number according to the  machine where you run Cyrus IMAP.

Su

-----Original Message-----
From: Rob Siemborski [mailto:rjs3 at andrew.cmu.edu]
Sent: October 31, 2002 10:38 AM
To: Su Li
Cc: Joe Finkle; info-cyrus at lists.andrew.cmu.edu
Subject: RE: Massive Problems (lmtp, db corruption) - Ahh!


On Thu, 31 Oct 2002, Su Li wrote:

> That will limit the number of lmtpd for sure. I tested with 10000 users
> and send email at 15 msg/sec. No problem found.

I agree, though I want to say it will limit all other processes as well
(though, you're the one who has tried this in practice, and don't seem to
have this problem).

> One more thing, the default maxchild is a number bigger thatn 200,000. I
> don't think any normal machine can handle that. We need to config the
> maxchild before it run.

I don't think that "unlimited" is an unreasonable default value for a
process count limit.

-Rob

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456
Research Systems Programmer * /usr/contributed Gatekeeper