spamassassin-dev October 2011 archive
Main Archive Page > Month Archives  > spamassassin-dev archives
spamassassin-dev: [Bug 6682] Using daemonize option writes wrong

[Bug 6682] Using daemonize option writes wrong PID (pid of parent process instead of child / daemon).

From: <bugzilla-daemon_at_nospam>
Date: Thu Oct 27 2011 - 12:48:12 GMT
To: dev@spamassassin.apache.org

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6682

--- Comment #4 from a-x-e@gmx.net 2011-10-27 12:48:12 UTC ---
(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.

-- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.