Marc Dirix wrote: > >> MAXCHILDREN limits how many connection can be established concurrently. >> Because any imap connection requires one child. MAXCONNECTS defines >> after >> how many connections a child gets killed. If i understand it right, one >> dbmail process can get very big(memory), when you deliver a big >> message. The >> memory used by a process get's only freeed completly, when the process >> terminates. This is what happens after MAXCONNECTS. At least i think >> so... >> :-) > > > I think memory is, and should be cleared after each connection is > closed, before starting to wait for a new connection.
That is the case, or at least it should be if it isn't! There are no known leaks in the code at the moment, and yes: we do check for them actively. > > Since today we encountered the maxconnects limit on our popserver, which > had setting 500 connections, it would be nice to have a setting > connect as much as you want, because setting the maxconnects to 2000 > resolved the problem without breaking anything else. That also means you had 2000 incoming connections on your database backend. Not a situation everyone will be able to accomodate. -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl
