----- Original Message -----
From: "Craig Morrison" <[EMAIL PROTECTED]>
To: "Jack Gostl" <[EMAIL PROTECTED]>
Cc: "spamassassin" <users@spamassassin.apache.org>
Sent: Thursday, November 23, 2006 3:01 PM
Subject: Re: saupdate
Jack Gostl wrote:
----- Original Message ----- From: "Craig Morrison" <[EMAIL PROTECTED]>
To: "Jack Gostl" <[EMAIL PROTECTED]>
Cc: "spamassassin" <users@spamassassin.apache.org>
Sent: Thursday, November 23, 2006 2:40 PM
Subject: Re: saupdate
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
I understand about RTFM, but there is so much new stuff introduced in
this release, I'm trying to catch up. What is funny is that I read all
the documentation, and this stuff just flew by me. Anyway, one final
thing, and I'm pretty sure this one isn't in the manual.
When I run sa-update, I get this message:
Use of uninitialized value in concatenation (.) or string at
/usr/opt/perl5/lib/5.8.2/Scalar/Util.pm line 30.
Not sure what to do about that one. Or if it even matters.
Jack
I can't comment on if it matters, but I am fairly certain from experience
the answer is most likely going to be upgrading Perl to at least 5.8.8..
Ugh! I'll give it a shot. Thanks for all your help.
