Re: other/3713: Piped Error Logs spawn extra process(es)

[dg...@apache.org]

[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]


Synopsis: Piped Error Logs spawn extra process(es)

State-Changed-From-To: feedback-analyzed
State-Changed-By: dgaudet
State-Changed-When: Wed Apr 21 10:36:33 PDT 1999
State-Changed-Why:
It's poorly (or not) documented that the piped log handler
has to handle SIGHUP, SIGUSR1, and SIGTERM.  All three are
shutdown signals.  But if there's a shell involved, as there
is when you do "| rotatelogs" you end up leaving orphans
around... because the shell exits but the child doesn't.

Dean
Synopsis-Changed-From: Piped Error Logs spawn extra process(es)
Synopsis-Changed-To: rotatelogs example does not handle SIGHUP, SIGUSR1, SIGTERM
Synopsis-Changed-By: dgaudet
Synopsis-Changed-When: Wed Apr 21 10:36:33 PDT 1999
Category-Changed-From-To: mod_log-any-other
Category-Changed-By: dgaudet
Category-Changed-When: Wed Apr 21 10:36:33 PDT 1999