Dean,
I was actually using a hacked version of rotatelogs--I just
sent the simple item as an example.
The rotatelogs.c file in the distribution should be updated to
handle this, or if exec would work for it as well, examples
of it with the ....Log directive should be updated to show
the exec.
Because we didn't understand this, we chose not to use piped
logging in our current release. With this knowledge, we may
revisit this issue at a later time,
--
thanks very much for the info,
sam
> From [EMAIL PROTECTED] Wed Apr 21 07:28 EDT 1999
> Return-Path: <[EMAIL PROTECTED]>
> Received: from attrh3.attrh.att.com by lynxhub.lz.att.com (5.x/EMS-1.2 sol2)
> id AA28199; Wed, 21 Apr 1999 07:28:17 -0400
> Received: by attrh3.attrh.att.com (8.8.8+Sun/ATTEMS-1.4.1 sol2)
> id HAA08973 for [EMAIL PROTECTED]; Wed, 21 Apr 1999 07:25:19 -0400 (EDT)
> Received: from ckmsi1.proxy.att.com by attrh3.attrh.att.com
> (8.8.8+Sun/ATTEMS-1.4.1 sol2)
> id HAA08946 for <[EMAIL PROTECTED]>; Wed, 21 Apr 1999 07:25:18 -0400
> (EDT)
> Received: from hyperreal.org ([209.133.83.16])
> by ckmsi1.proxy.att.com (AT&T IPNS/GW-2.2) with SMTP id HAA25066
> for <[EMAIL PROTECTED]>; Wed, 21 Apr 1999 07:31:55 -0400 (EDT)
> Received: (qmail 19653 invoked by uid 2012); 21 Apr 1999 04:25:09 -0000
> Date: 21 Apr 1999 04:25:09 -0000
> Message-Id: <[EMAIL PROTECTED]>
> To: apache-bugdb@apache.org, [EMAIL PROTECTED], [EMAIL PROTECTED]
> From: [EMAIL PROTECTED]
> Subject: Re: mod_log-any/3713: Piped Error Logs spawn extra process(es)
> Content-Type: text
> Content-Length: 986
>
> [In order for any reply to be added to the PR database, ]
> [you need to include <[EMAIL PROTECTED]> 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
