Re: Logging with Syslog

[sa-list]

Thanks! 

Instead of messing with the /etc/sysconfig/spamassassin file, I just 
commented out those lines. Any reason to keep this configuration, other than 
wanting more headaches in the future when I try to figure this out again? 

Kris Deugau writes: 

sa-list wrote:
I can't seem to get SA & Syslog to log messages to a log file other than
maillog.
I changed the spamassassin start up script to add "-s local5" to the
spamd start up options.

[snip] 

... on RHEL4.

[snip] 

The top part of my /etc/init.d/spamassassin is:

[snip]
# Set default spamd configuration.
SPAMDOPTIONS="-d -m5 -H -s local5"
SPAMD_PID=/var/run/spamd.pid
# Source spamd configuration.
if [ -f /etc/sysconfig/spamassassin ] ; then
       . /etc/sysconfig/spamassassin
fi

This is the part of the init script that's tripping you up. 

Most RH-oriented init scripts are managed by the packaging system, and
among other things will usually be overwritten by package upgrades. 

Thus the last three lines in that segment;  it overrides the package
default options with whatever you set in /etc/sysconfig/spamassassin.
In this case, it also overrides the change you made in the previous lines. 

Add your "-s local5" to the SPAMDOPTIONS definition in
/etc/sysconfig/spamassassin, and you should get your syslog output in
the right place. 

ps x|grep spamd should show you the full command line of the
currently-running spamd. 

-kgd