DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8261>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8261 CustomLog within Directory*, Location* and Files* containers [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From [EMAIL PROTECTED] 2002-06-15 06:10 ------- The best way to do this type of thing, is to run a script on the log files after they have been written, or to use piped logs. The biggest problem with this idea, is that EVERY CustomLog directive requires a separate file. If we allow a CustomLog inside of <directory>, <location>, and <files> containers, it will be very easy to run out of file descriptors very quickly. Beyond that, the logging modules are not designed to solve every possible problem, they are designed to do as little as possible, and allow for external programs to solve the harder problems. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
