Return-Path: 
 <cvs-return-13932-apmail-httpd-cvs-archive=httpd.apache.org@httpd.apache.org>
Delivered-To: apmail-httpd-cvs-archive@httpd.apache.org
Received: (qmail 55306 invoked by uid 500); 21 Nov 2002 21:06:58 -0000
Mailing-List: contact cvs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
list-help: <mailto:cvs-help@httpd.apache.org>
list-unsubscribe: <mailto:cvs-unsubscribe@httpd.apache.org>
list-post: <mailto:cvs@httpd.apache.org>
Delivered-To: mailing list cvs@httpd.apache.org
Received: (qmail 55295 invoked by uid 500); 21 Nov 2002 21:06:58 -0000
Delivered-To: apmail-httpd-2.0-cvs@apache.org
Date: 21 Nov 2002 21:06:57 -0000
Message-ID: <20021121210657.73411.qmail@icarus.apache.org>
From: slive@apache.org
To: httpd-2.0-cvs@apache.org
Subject: cvs commit: httpd-2.0/docs/manual logs.xml
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

slive       2002/11/21 13:06:57

  Modified:    docs/manual logs.xml
  Log:
  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.
  
  Revision  Changes    Path
  1.6       +5 -16     httpd-2.0/docs/manual/logs.xml
  
  Index: logs.xml
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/logs.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -d -b -u -r1.5 -r1.6
  --- logs.xml	19 Sep 2002 18:02:35 -0000	1.5
  +++ logs.xml	21 Nov 2002 21:06:57 -0000	1.6
  @@ -474,22 +474,6 @@
       that piped log programs usually run as root. It is therefore
       very important to keep the programs simple and secure.</p>
   
  -    <p>Some simple examples using piped logs:</p>
  -
  -    <example>
  -      # compressed logs<br />
  -      CustomLog "|/usr/bin/gzip -c &gt;&gt;
  -      /var/log/access_log.gz" common<br />
  -      # almost-real-time name resolution<br />
  -      CustomLog "|/usr/local/apache/bin/logresolve &gt;&gt;
  -      /var/log/access_log" common
  -    </example>
  -
  -    <p>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.</p>
  -
       <p>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 <a
  @@ -502,6 +486,11 @@
         /var/log/access_log 86400" common
       </example>
       
  +    <p>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.</p>
  +
       <p>A similar, but much more flexible log rotation program
       called <a href="http://www.cronolog.org/">cronolog</a>
       is available at an external site.</p>