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 12386] - CustomLog: piping to gzip does not work as documented
Date Sat, 07 Sep 2002 18:49:12 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=12386>.
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=12386

CustomLog: piping to gzip does not work as documented





------- Additional Comments From jc@mega-bucks.co.jp  2002-09-07 18:49 -------
I *wish* I could help. Piping to gzip would be godsend for me as my logs get
quite large (>1GB/day) and are causing a Disk I/O bottleneck. I have lots of CPU
to spare ...

Oh! Hey, gzip can't compress a file without knowing all of the data first ... it
needs to scan all the data first so that it can come up with a good compression
scheme.

So until the stream is closed gzip just can't do anything?

That would seem to make sense except that even if I stop apache the log file
never receives anything if I try to pipe the log to gzip.

If you can spare the cycles please look into it ... piping to gzip wouldb be
*very* nice.

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


Mime
View raw message