On Tue, Jan 11, 2005 at 09:14:03AM +0000, Martin Hepworth wrote:
> Bill
> 
> 
> Alot of people seem to be noticed this, there is a small memory patch 
> floating around the email list archives you could try.

Do you remember any good keywords subject or author to help in
locating the patch?  I'm not having much luck searching.

By the way, I set --max-conn-per-child=20 (yes, very low) and that
seems to have solved the problem with a given spamd process eating
memory.

But I'm still seeing a lot of:

    Jan 11 10:03:57 mardy spamd[13158]: server hit by SIGCHLD
    Jan 11 10:03:57 mardy spamd[13158]: handled cleanup of child pid 27032
    Jan 11 10:03:57 mardy spamd[13158]: server successfully spawned child 
process, pid 30366
    Jan 11 10:03:57 mardy spamd[13158]: server hit by SIGCHLD
    Jan 11 10:03:57 mardy spamd[13158]: handled cleanup of child pid 27032
    Jan 11 10:03:57 mardy spamd[13158]: server successfully spawned child 
process, pid 30366
    Jan 11 10:03:57 mardy spamd[13158]: server hit by SIGCHLD
    [...]

Is that a result of the child process being killed by
--max-conn-perl-child?


Thanks,

-- 
Bill Moseley
[EMAIL PROTECTED]

Reply via email to