Mailing-List: contact apache-bugdb-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: apache-bugdb@apache.org
Date: 28 Apr 2001 17:18:38 -0000
Message-ID: <20010428171838.43699.qmail@apache.org>
To: apache-bugdb@apache.org, marc@apache.org, rwhite@collectivenet.net
From: marc@apache.org
Subject: Re: general/7646: Request Feature in mod_vhost_alias (Log Files)

[In order for any reply to be added to the PR database, you need]
[to include <apbugs@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database 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: Request Feature in mod_vhost_alias (Log Files)

State-Changed-From-To: open-closed
State-Changed-By: marc
State-Changed-When: Sat Apr 28 10:18:38 PDT 2001
State-Changed-Why:
It is not practical for the regular logging directives to allow such logfiles because that would significantly change the semantics of how logging works; right now, logs are opened once and are opened before Apache setuid()s to the user it runs as.  These semantics are unlikely to change since they are there for various good reasons.

You could use the piped logging feature to have Apache send the access logs to an external program, which can then split them out however you want, without the code having to be internal to Apache.