From e4b5584f81f9f4467ff2a01e64dbdbd6d3991f6e Mon Sep 17 00:00:00 2001 From: Joshua Slive Date: Thu, 21 Nov 2002 21:06:57 +0000 Subject: [PATCH] I never adequately tested these examples when writing logs.xml, and I've heard from a couple places that these examples don't work very well. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@97588 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/logs.xml | 21 +++++---------------- 1 file changed, 5 insertions(+), 16 deletions(-) diff --git a/docs/manual/logs.xml b/docs/manual/logs.xml index 37e2774363..2aba77549a 100644 --- a/docs/manual/logs.xml +++ b/docs/manual/logs.xml @@ -474,22 +474,6 @@ that piped log programs usually run as root. It is therefore very important to keep the programs simple and secure.

-

Some simple examples using piped logs:

- - - # compressed logs
- CustomLog "|/usr/bin/gzip -c >> - /var/log/access_log.gz" common
- # almost-real-time name resolution
- CustomLog "|/usr/local/apache/bin/logresolve >> - /var/log/access_log" common - - -

Notice that quotes are used to enclose the entire command - that will be called for the pipe. Although these examples are - for the access log, the same technique can be used for the - error log.

-

One important use of piped logs is to allow log rotation without having to restart the server. The Apache HTTP Server includes a simple program called +

Notice that quotes are used to enclose the entire command + that will be called for the pipe. Although these examples are + for the access log, the same technique can be used for the + error log.

+

A similar, but much more flexible log rotation program called cronolog is available at an external site.

-- 2.40.0