Re: Master prefork problems; CLOSE_WAIT problems

2002-05-05 Thread Jeremy Howard
Helmut Apfelholz wrote: >>I've found a way to fix this. In master.c >>reap_child, add: >> >> c->s->ready_workers--; >> >>and >> >> t->s->ready_workers--; >> >>...immediately after the corresponding nactive--. >>This resolves the >>problem for me in the limited testing I've done to >>date. >>

Re: Master prefork problems; CLOSE_WAIT problems

2002-05-05 Thread Helmut Apfelholz
Hi, --- Jeremy Howard <[EMAIL PROTECTED]> wrote: > Jeremy Howard wrote: > > > I've seen a couple of problems over the last few > weeks with master > > apparently failing to correctly maintain the > prefork pool. We > > particularly see this problem with pop3d, which > has more > > connects/d

Re: Master prefork problems; CLOSE_WAIT problems

2002-05-02 Thread Scott Adkins
--On Thursday, May 02, 2002 9:52 AM +1000 Jeremy Howard <[EMAIL PROTECTED]> wrote: > I've seen a couple of problems over the last few weeks with master > apparently failing to correctly maintain the prefork pool. We > particularly see this problem with pop3d, which has more > connects/disconnect

Re: Master prefork problems; CLOSE_WAIT problems

2002-05-01 Thread Jeremy Howard
Jeremy Howard wrote: > I've seen a couple of problems over the last few weeks with master > apparently failing to correctly maintain the prefork pool. We > particularly see this problem with pop3d, which has more > connects/disconnects than IMAP because of the nature of the protocol. <...>

Master prefork problems; CLOSE_WAIT problems

2002-05-01 Thread Jeremy Howard
I've seen a couple of problems over the last few weeks with master apparently failing to correctly maintain the prefork pool. We particularly see this problem with pop3d, which has more connects/disconnects than IMAP because of the nature of the protocol. The first issue is that in shut_down()