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 2002/09/07 06:46:33 UTC
DO NOT REPLY [Bug 12386] New: -
CustomLog: piping to gzip does not work as documented
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
Summary: CustomLog: piping to gzip does not work as documented
Product: Apache httpd-1.3
Version: 1.3.26
Platform: PC
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Documentation
AssignedTo: bugs@httpd.apache.org
ReportedBy: jc@mega-bucks.co.jp
The docs at: http://httpd.apache.org/docs/logs.html
state that the following directive will cause apache to pipe it's logs to gzip
before writing them to disk.
CustomLog "|/usr/bin/gzip -c >> /var/log/access_log.gz" common
I have tried this directive on apache 1.3.26 running on RH Linux with kernel
2.4.7-10 and it does *not* work. All I get is a 20 byte file called
access_log/gz being created and nothing ever gets written to it. Gunzip'ing the
file give me a 0 byte file.
This is either a bug in apache or the docs.
Others have reported the same problem on the ML but no one seems to have found a
reason or solution.
Thanks!
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org