> 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
> Is that a result of the child process being killed by
> --max-conn-perl-child?
Its a result of reaching the max number of connections per child, and is
perfectly normal, despite looking like an error. I think I may have opened
a bug to make this look less like an error, but I don't recall for sure if I
did or not.
You would see this (eventually) even without setting max conn, it would just
take longer.
Loren
BTW, this probably means that you have a really big whitelist or bayes db,
and possibly expire isn't working as you think it is. Might be worth
checking on that.
