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 13511] - Apache misbehaves if log files can't be written
Date Thu, 17 Oct 2002 13:30:43 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=13511>.
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=13511

Apache misbehaves if log files can't be written





------- Additional Comments From slive@apache.org  2002-10-17 13:30 -------
I don't understand your first paragraph at all.  How does multiple CGI
processes have anything to do with it?  They are all handled identically.

Regarding behaving better when the error log is full, that seems
kind of absurd to me.  Apache writes errors to the the error log.
If it can't do that, what is it supposed to do?  Write to another
log file?  What if that log can't be written to?  Send a message to
your pager?  Walk down the hall and tap you on the shoulder? ;-)

At some point it needs to be the administrator's responsibility
to maintain available system resources.

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


Mime
View raw message