Re: mod_log-any/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: open-feedback
State-Changed-By: dgaudet
State-Changed-When: Tue Apr 20 21:25:08 PDT 1999
State-Changed-Why:
Yeah, it's poorly documented, but the piped log child is
also sent SIGUSR1, SIGHUP, and SIGTERM when you send the
respective signals to the parent.  The child needs to handle
them (essentially trap them and clean up properly).

In your case if you just stick an "exec" in front of the grep
I think everything will work just fine.

Dean