jplesset wrote:
Oban, I'm having a somewhat similar issue, though a different environment.
SpamAssassin 3.0.1, Solaris 9, and iPlanet Messaigng 5.2p2. I find that when I started spamd,with no special flags, other than -d, I got a large number of spamd processes running. This number increased over about 20 minutes, to fill my available ram and swap.
I seem to have stabilized my situation, now.
I start spamd with
spamd -m 2 --max-conns-per-child=3
and I seem to have somthing like 10 to 12 spamd processes all the time. At least, it's not growing. . .
You might want to give that a try.
Ok, this seems to be a *lot* more stable from a memory standpoint:
"spamd -m 3 --max-conn-per-child=3"
But now I'm seeing this in my mail logs every few seconds:
----------------------------------------------------------------
Nov 3 15:46:58 mail spamd[18881]: server hit by SIGCHLD
Nov 3 15:46:58 mail spamd[18881]: handled cleanup of child pid 21042
Nov 3 15:46:58 mail spamd[18881]: server successfully spawned child process, pid 21219
----------------------------------------------------------------
Should I worry about it? Or is this good?
