On Friday 12 September 2003 04:02 pm, Robin Lynn Frank wrote:
> I installed 2.60 rc4 over 2.55 which had not been used. This is the
> result:
>
> PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ Command
> 26711 omega13 15 0 27324 23m 13m R 30.3 13.2 1:22.34 spamd
> 26559 omega
I installed 2.60 rc4 over 2.55 which had not been used. This is the result:
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ Command
26711 omega13 15 0 27324 23m 13m R 30.3 13.2 1:22.34 spamd
26559 omega13 18 0 26624 17m 7972 R 30.0 9.6 9:23.79 spamd
The only changes
I am running spamassassin 2.55 out of spamass-milter 0.2.0, and I
recently had a problem in which spamd went crazy because it couldn't
write to a user's Bayes journal. Is there a way to have spamd give up
if it can't write to the journal? Below are detail of exactly what
happened.
As I said, spa
I recently installed spamassassin (debian testing, using postfix and
procmail), and have been getting this phenomenon where I get lots of
spamd processes that basically take the server over, and slow things
down hugely. I've had some spamd processes that were lasting 5-10
minutes!
I "disconnec
I am running the CVS
2.50 SpamAssassin from 2 days ago
When I run the
command /etc/init.d/spamassassin restart spamd begins to accumulate in the
process list. When I check the mail error log, I see:
spamc[21775]:
connect() to spamd at 127.0.0.1 failed, retrying (1/3): Connect
