On Thu, Dec 02, 2004 at 04:25:46PM -0300, Matias Lopez Bergero wrote:From time to time, some spamd process sticks on top of the top listingwith an ~90% CPU utilization, like this:
27639 mselig 39 19 30104 29M 2472 R N 105.2 1.9 60:04 0 spamd
There is a way to prevent this?
Possibly.
Depending on your setup you could turn off bayes_auto_expire and do the expiration manually (ie sa-learn --force-expire), at a time that you control. Unfortunately, unless you are running a sitewide bayes config, this may not work well with a lot of individual bayes dbs.
I have disabled the bayes_auto_expire from spamd conf, and run the sa-learn --force-expire but I still get some spamd process that uses many CPU resources for a very long time(until I kill them).
The only thing that I found curious, is that I always see the same user running this spamd processes with high CPU usage.
Normally the was only a single process of spamd killing my CPU, but now there are many.
3090 mselig 25 0 29112 28M 2564 R 49.6 1.8 3:46 1 spamd 28737 mselig 25 0 30604 29M 2564 R 48.1 1.9 42:35 0 spamd 28103 mselig 25 0 32168 31M 2564 R 46.5 2.0 13:24 1 spamd 31333 mselig 25 0 31732 30M 2564 R 45.0 2.0 22:43 1 spamd
This is happening since I disable the bayes_auto_expire.
I'm doing something wrong here?
On the spamd configuration file I have only defined the languages, the mount of score that a mail must to have to be flagged as spam, and the bayes_auto_expire to 0.
Do I need to configure anything else??
BR, Matías.
