You are viewing a plain text version of this content. The canonical link for it is here.

Posted to bugs@httpd.apache.org by bu...@apache.org on 2003/02/14 22:41:33 UTC

DO NOT REPLY [Bug 13511] - Apache misbehaves if log file reaches 2GB

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 file reaches 2GB

trawick@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Apache misbehaves if log    |Apache misbehaves if log
                   |files can't be written      |file reaches 2GB



------- Additional Comments From trawick@apache.org  2003-02-14 21:41 -------
This is the 2GB log file problem :(

32-bit builds of Apache (1.3 or 2.0) don't currently handle "large" files. 
Apache child processes will die trying to write logs which have reached 2GB in
size.  The obvious place to report the proble is -- you guessed it -- the
log file that we can't write to.

The current message to users is that they need to use log rotation to keep the
size well under 2GB.

Yes this sucks, yes it will eventually get fixed, yes there are issues that make
it problematic to enable on some platforms (including Linux).

Sorry :(

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