Mailing List Archive

Author: jm
Date: Mon Apr 11 18:00:41 2005
New Revision: 160995

URL: http://svn.apache.org/viewcvs?view=rev&rev=160995
Log:
added note about SIGHUP required when syslogd is restarted

Modified:
spamassassin/trunk/spamd/spamd.raw

Modified: spamassassin/trunk/spamd/spamd.raw
URL: http://svn.apache.org/viewcvs/spamassassin/trunk/spamd/spamd.raw?view=diff&r1=160994&r2=160995
==============================================================================
--- spamassassin/trunk/spamd/spamd.raw (original)
+++ spamassassin/trunk/spamd/spamd.raw Mon Apr 11 18:00:41 2005
@@ -2327,11 +2327,11 @@
changes to the system-wide config files will require either restarting spamd
or forcing it to reload itself via B<SIGHUP> for the changes to take effect.

-Note: If C<spamd> receives a B<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 B<SIGHUP>, you should always start C<spamd> with the B<-r> switch to know its
-current pid.
+Note: If C<spamd> receives a B<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 B<SIGHUP>, you should always start C<spamd> with the B<-r>
+switch to know its current pid.

=head1 OPTIONS

@@ -2486,6 +2486,11 @@
Note that logging to a file does not use locking, so you cannot intermix
logging from spamd and other processes into the same file. If you want
to mix logging like this, use syslog instead.
+
+If you use syslog logging, it is essential to send a SIGHUP to the spamd daemon
+when you restart the syslogd daemon. (This is due to a shortcoming in Perl's
+syslog handling, where the disappearance of the connection to the syslogd is
+considered a fatal error.)

=item B<--syslog-socket>=I<type>