> > Recently I posted about limiting my spamd processes to a > certain maximum. I tried to enforce this by adjusting my > startup script for spamd. See the following: > > SPAMDOPTIONS="-m 12 -d -c -u spamd" > > This morning I watched over 20 spamd processes running at the > same time. Eventually all my memory (ram and swap) gets > sucked up and the box becomes a pile of mush. It seems that > only perl and calmscan process then run. Any ideas? >
This wont be an issue in 3.0, as the children are pre forked... If this is a hibitual problem for you (like it was for me), move to 3.0 early... I've been running it for over a month, and it much more stable than 2.63 ever was (for me at least). Dallas
