http://bugzilla.spamassassin.org/show_bug.cgi?id=3507
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WORKSFORME
------- Additional Comments From [EMAIL PROTECTED] 2005-01-21 12:20 -------
btw, the normal way to deal with this is for SIGCHLD to be set to 'DEFAULT' or
'IGNORE'. by default, it's 'DEFAULT' (obviously). those builtin signal
handlers do not exit the process when a SIGCHLD is received, as that's a normal
IPC signal and non-fatal by any means.
I'd suggest fixing the upstreams, but in the meantime I'll put something into
3.1.0 along the lines you've described (ie. a scoped signal handler for helper
apps). as Michael says, pls check with 3.0.0 too.
marking WORKSFORME...
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
