I can only say that i have the same problem with my debian machine and
i have no answer why?? how long needs the same sample-spam file with
spamassasin -D ??
Josh Trutwin wrote:
On Thu, 17 Jun 2004 12:39:36 -0500
"Todd Schuldt" <[EMAIL PROTECTED]> wrote:
<snip>
Sounds like you are spawning into a lot child processes and hitting
the swap file. Try limiting the number of child processes ( -m # I
believe) to something reasonable at first (say 10) and see if it
helps, then adjust upward from there if it does.
Thanks, I updated spamd to run as follows:
spamd -d -D -q -x -L --socketpath=/var/spool/spamassassin/spamd.sock -m 6 -u spamd
date ; spamc -f -U /var/spool/spamassassin/spamd.sock -u "[EMAIL PROTECTED]" < sample-spam.txt ; date
Thu Jun 17 13:01:08 CDT 2004
<report content snipped>
Thu Jun 17 13:04:28 CDT 2004
3+ minutes - better than 10, but still pretty dang long. This machine is a dual proc (2 2.4 Ghz Xeon) with a Gig of memory running very few other programs (mysql, apache, qmail), I can't believe that this is a hardware limitation.
Any other thoughts?
Josh
|
