Ok, nearly there. :) I start spamd 3.1.6 as follows:
/usr/local/bin/spamd -D -x -q -d -m 16 -r /var/run/spamd.pid -i 127.0.0.1
-A 127.0.0.1 -u spamd -s mail.crit
I get:
[11581] dbg: logger: adding facilities: all
[11581] dbg: logger: logging level is DBG
[11581] dbg: logger: successfully
/usr/local/bin/spamd -D -x -q -d -m 16 -r /var/run/spamd.pid -i 127.0.0.1
-A 127.0.0.1 -u spamd -s mail.crit
I can't answer your questions, but that -m 16 has me worried. At around
40-60 megs per child, that is using up a LOT of ram. Unless you have a few
gigs spare on this machine I'd
-Original Message-
From: Loren Wilton [mailto:[EMAIL PROTECTED]
Sent: vrijdag 6 oktober 2006 10:16
To: users@spamassassin.apache.org
Subject: Re: Syslog gone?
Well, I got my syslog back. Apparently, 3.1.6 no longer accepts facility
in the form of mail.crit (facility + severity
Well, I got my syslog back. Apparently, 3.1.6 no longer accepts facility
in the form of mail.crit (facility + severity; 2.55 did). But using a
single word facility like debug or some such works fine.
Yep. Facility coding scheme changed about three releases back as best I
recall. You might
Title: RE: Syslog gone?
-Original Message-
From: Loren Wilton [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 06, 2006 4:15 AM
To: users@spamassassin.apache.org
Subject: Re: Syslog gone?
/usr/local/bin/spamd -D -x -q -d -m 16 -r
/var/run/spamd.pid -i 127.0.0.1
Chris wrote:
I can't answer your questions, but that -m 16 has me worried.
At around
40-60 megs per child, that is using up a LOT of ram. Unless
you have a few
gigs spare on this machine I'd stick with the default of 5
children until
you have things up and running
