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 29243] - Logs hitting max file size limit cause server to fail without reporting anything useful...
Date Thu, 03 Jun 2004 21:48:43 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=29243>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29243

Logs hitting max file size limit cause server to fail without reporting anything useful...

jorton@redhat.com changed:

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



------- Additional Comments From jorton@redhat.com  2004-06-03 21:48 -------
mod_log_config writes the error to the error_log, I can't reproduce a problem
here with 2.0.49, it looks like shows up in your truss output too:

write(21, " [ T h u   M a y   2 7  ".., 167)    = 167

e.g. by making an access_log into a directory, I get in error_log:

[Thu Jun 03 22:43:39 2004] [error] (21)Is a directory: could not open transfer
log file /etc/httpd/logs/access_log.
Unable to open logs

I think that's the best the module can do.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message