> I just noticed the --max-conn-per-child option in the spamd man page.
While
> the description is fairly straightforward, I'm curious if anyone else is
> using this
Yes, many people
, why, and if it's helped with spamd processes consuming RAM
> (which is what I'm trying to fix at the moment).
Which is why people are using it. In 3.0.1 and to a lesser extent in 3.0.2,
spamd children could get real fat and stay that way for a long time, eating
the machine for dinner. Setting max-con-per-child to a lower number will
make the fat kids die quicker, so there is much less chance of them all
being fat at once.
Depending on the weather, phase of the moon, amount of ram you have, and
other things, you may find limits from a couple hundred down to about 5 to
be appropriate. I'd probably suggest 100 to 50 as a good starting range to
play with.
Dont forget the -m option. If you have more than about 5 children running
and don't have a huge email flow you might do well to cut the number of
children down to the 3 to 10 range.
Loren
