From:
[email protected]
I too have had problems on a recent spamassassin installation, where it consumed all of the resources of the machine and I was unable to get
into it (load shot up to well over 20).
I'd suggest that merely changing the defaults on the configuration file
would be sufficient to not cause so many people this problem at the
start - if they then tweak the parameters, that woudl be their look-out
and they'd be expecting it.
I've altered my /etc/default/spamassassin to have:
OPTIONS="-c -m 3 -a -H"
(i.e. only three spamd at any one time)
NICE="--nicelevel 15
(i.e. enable the uncommented nice level)
Not sure if you can use this to close this bug or not, but it would seem
a more sensible default to have. (You could also change the first line
to read "# /etc/default/spamassassin".)
(All this for my spamassassin-2.63-1)
BR,
Millis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQBBH0YxPiGAmnxCk08RAr4PAJ0eNyUykEDAnqwBb0gsjaklQ1jryQCeNNcZ 5KuxBUYOfqQ7R/3GDh1A8XU=
=mZII
-----END PGP SIGNATURE-----
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)