Folks:
Right in the spamd FM it says:
-u username...
...
Note: If this option is set to a non-root user, and spamd is to run on a
privileged port (any < 1024, default 783 or via -p), the parent will not
be able to be sent a SIGHUP to reload the configuration.
Sigh. I thought I had read this more closely than I obviously had!
rnd
-----Original Message-----
From: Diffenderfer, Randy
Sent: Monday, March 07, 2005 1:58 PM
To: '[email protected]'
Subject: Problem getting SA 3.0.2 to restart
Folks:
I invoke spamd using the following command line (as root):
/path/to/spamd -d -x -L -u sauser -s local2 -r /var/run/spamassassin/spamd.pid
The pid directory is accessible/writable by the sauser and the file does get created with contents as expected.
I try to force a reload by sending a SIGHUP to the process noted in spamd.pid. The logs reflect spamd closing down and trying to start up, but it never gets up again...
<log snip>
Mar 4 16:32:09 ahtst2 spamd[6333]: server started on port 783/tcp (running version 3.0.2)
Mar 4 16:32:09 ahtst2 spamd[6333]: server successfully spawned child process, pid 6334
Mar 4 16:32:09 ahtst2 spamd[6333]: server successfully spawned child process, pid 6335
Mar 4 16:32:09 ahtst2 spamd[6333]: server successfully spawned child process, pid 6336
Mar 4 16:32:09 ahtst2 spamd[6333]: server successfully spawned child process, pid 6337
Mar 4 16:32:09 ahtst2 spamd[6333]: server successfully spawned child process, pid 6338
Mar 4 16:32:47 ahtst2 spamd[6333]: server hit by SIGHUP, restarting
Mar 4 16:32:47 ahtst2 spamd[6333]: child 6334 killed successfully
Mar 4 16:32:47 ahtst2 spamd[6333]: child 6335 killed successfully
Mar 4 16:32:47 ahtst2 spamd[6333]: child 6336 killed successfully
Mar 4 16:32:47 ahtst2 spamd[6333]: child 6337 killed successfully
Mar 4 16:32:47 ahtst2 spamd[6333]: child 6338 killed successfully
Mar 4 16:32:48 ahtst2 spamd[6333]: spamd starting
<end of log snip>
This is what I *don't* see (a usccessful startup):
<log snip>
Mar 4 16:34:41 ahtst2 spamd[6388]: spamd starting
Mar 4 16:34:42 ahtst2 spamd[6390]: server started on port 783/tcp (running version 3.0.2)
Mar 4 16:34:42 ahtst2 spamd[6390]: server successfully spawned child process, pid 6391
Mar 4 16:34:42 ahtst2 spamd[6390]: server successfully spawned child process, pid 6392
Mar 4 16:34:42 ahtst2 spamd[6390]: server successfully spawned child process, pid 6393
Mar 4 16:34:42 ahtst2 spamd[6390]: server successfully spawned child process, pid 6394
Mar 4 16:34:42 ahtst2 spamd[6390]: server successfully spawned child process, pid 6395
<end of log snip>
Anybody else have similar experiences?
rnd
