Please keep replies on the list for the benefit of others.. Comments
inline..
Jack Gostl wrote:
Question 2:
After running saupdate, I assume that all I have to do is to restart
spamd. How can I force spamd to restart and reload its rules? Can a
do a simple kill -1? Or do I need an actual kill and restart?
That is highly dependent upon how spamd is invoked.
--
Craig
Thanks for the response.
It was invoked through /etc/inittab with the command:
spam:2:once:/usr/opt/perl5/bin/spamd -m20 -d -A 10.165.1.3,127.0.0.1 -i
Which means no automatic respawning. So does spamd respond to a SIGHUP
by restarting?
`man spamd':
"DESCRIPTION
The purpose of this program is to provide a daemonized version
of the spamassassin executable. The goal is improving throughput
performance for automated mail checking.
This is intended to be used alongside "spamc", a fast,
low-overhead C client program.
See the README file in the "spamd" directory of the SpamAssassin
distribution for more details.
Note: Although "spamd" will check per-user config files for
every message, any changes to the system wide config files will require
either restarting spamd or forcing it to reload itself via SIGHUP for
the changes to take effect.
Note: If "spamd" receives a SIGHUP, it internally reloads
itself, which means that it will change its pid and might not restart at
all if its environment changed (ie. if it can’t change back into its
own directory). If you plan to use SIGHUP, you should always start
"spamd" with the -r switch to know its current pid."
I'm usually not a RTFM prude, however, SpamAssassin is VERY well
documented in its manual pages.
--
Craig