httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 8261] - CustomLog within Directory*, Location* and Files* containers
Date Sat, 15 Jun 2002 06:10:31 GMT
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

rbb@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX



------- Additional Comments From rbb@apache.org  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: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message