[clue-admin] SpamAssasin is Really Bogging the Server

[Jeff Cann]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 14 March 2005 4:20 pm, Jed S. Baer wrote:
> Not really sure how much effect changing priority would do. Depends on the
> kernel scheduling algorithm. But I doubt it would hurt.

When I ran the /etc/init.d/spamassassin script in shell debug, I did see that 
Jed's assumption was correct - setting the NICELEVEL does cause the script to 
use nice to spawn spamd.  Without that env variable, it uses daemon to spawn.  

So, when I tried setting the NICELEVEL in /etc/sysconfig/spamassassin and  
restarted the spamassassin service, it failed.

	Starting spamd: execvp: No such file or directory

It looks like a command line parameter is not being set correctly when we try 
to spawn with nice.

I'll have to figure out why this isn't working.  I'll consult the spamassassin 
manual.  For now, I turned it back on with the default priority of zero.

While spamd was not running, I watched top for a while.  I noticed that python 
jobs from mailman are consuming what seems to me an inordinate amount of CPU 
- - over 90% of the CPU:

25390 mailman   25   0  126m 121m 6768 R 96.2 38.6   2:52.70 python

I wonder if changing the priority of mailman would be [more] useful.

Or as Jed suggested, up the priority of httpd.

Jeff
- -- 
"Science can purify religion from error and superstition. Religion can purify 
science from idolatry and false absolutes."
- - Pope John Paul II

http://isuma.org/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFCO8dzi4b9OApLCmoRAr0GAJ488gXNUXFWqUpbnBclIc1m3qtwmwCcCxlJ
WaCLD9I/oOOxgUL/QSaOKw4=
=Qux9
-----END PGP SIGNATURE-----