Qnet .. wrote: > I start : > > #!/bin/sh > # spamassassin This script starts and stops the spamd daemon > # > > PATH=$PATH:/usr/local/sbin:/usr/local/bin > case "$1" in > start) > cd / > > /usr/bin/spamd -v -u vpopmail -m 60 -x -q -s stderr -r > /var/run/spamd/spamd.pid \ > -i 172.16.10.14 -A 172.16.10.0/24 2>&1 | \ > /usr/local/bin/setuidgid qmaill \ > /usr/local/bin/multilog t !spamdappend /var/log/qmail/spamd & > echo "spamd started"
60 is *WAY* too many spamd children unless you've got a *VERY* beefy system. Try modifying that "-m 60" to something more sane, like the default, which would be "-m 5". If you've got a lot of mail going through, 5 won't handle it, so for that I might start at 15. If your mail starts backing up, you can increase the number of spamd children, but be aware that too many will just grind your system to a halt. Try adding spamd children in increments of 5, and watch the "top" output. Your swap used should never be more than mem free if you can avoid it. You've got a gig of ram, and your spamds are 30mb a pop or so... you should be ok up to about 20-25 spamd children, depending on how much other stuff is eating your memory, but you'll quickly run into trouble if you go over 30. (30 spamds at 30mb each is 900mb of ram.. probably the absolute max you can fit even if the server isn't doing anything else but mail..)
