https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6682
--- Comment #5 from Kevin A. McGrail <[email protected]> 2011-10-27 16:03:46 UTC --- (In reply to comment #4) > (In reply to comment #3) > > > > What OS are you using? > > It is a hosted virtual server, OS is Suse 9.1 (old, but nearly everything > running on it continously manually updated) with a 2.4.20 kernel. > > > > SIGUSR1 is a reserved signal so it should let SA do what > > it wants with the signal. A SIGTERM just terminates the process. At least > > that's my understanding. > > I have same understanding. But if I am write terminating the parent process > after daemonizing is exactly waht should be done. > > - Parent process gets started > - Parent process "daemonizes" which results in a parent process > - Parent process will be terminated > - child process continues running > > > In spamd code I could not found any special handling for SIGUSR1. Please run spamd --username=httpd --daemonize --max-children 5 --pidfile=/tmp/spamd_full.pid --socketpath=/tmp/spamd_full.sock from the command line It should exit to the command line after a minute. When that's done, what is the output of cat /tmp/spamd_full.pid and ps auxwww | grep spam? -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
