Re: imapd and pop3d processes accumulate when clients disappear

2011-01-11 Thread Sebastian Hagedorn
--On 11. Januar 2011 07:26:38 -0600 Gary Mills wrote: On Mon, Jan 10, 2011 at 11:39:31PM +0100, Sebastian Hagedorn wrote: That was fixed quite a while ago ... we had the same problem, so I worked with one of the developers to debug and fix it. Thanks for the information. So, a Cyrus or SA

Re: imapd and pop3d processes accumulate when clients disappear

2011-01-11 Thread Gary Mills
On Mon, Jan 10, 2011 at 11:39:31PM +0100, Sebastian Hagedorn wrote: > > That was fixed quite a while ago ... we had the same problem, so I > worked with one of the developers to debug and fix it. Thanks for the information. So, a Cyrus or SASL upgrade some time in the future should fix this prob

Re: imapd and pop3d processes accumulate when clients disappear

2011-01-10 Thread Sebastian Hagedorn
That was fixed quite a while ago ... we had the same problem, so I worked with one of the developers to debug and fix it. Am 10.01.2011 um 23:23 schrieb Gary Mills : > I've noticed on our murder front end that imapd and pop3d processes > gradually accumulate. Some of these can be several months

imapd and pop3d processes accumulate when clients disappear

2011-01-10 Thread Gary Mills
I've noticed on our murder front end that imapd and pop3d processes gradually accumulate. Some of these can be several months old. In both cases, the reason seems to be that the process is listening on standard input, but the client has disappeared. Here's a typical stack trace: # pstack 58