httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r988071 - in /httpd/httpd/trunk/docs/manual: logs.xml mod/core.xml mod/mod_log_config.xml
Date Mon, 23 Aug 2010 11:13:24 GMT
Author: rjung
Date: Mon Aug 23 11:13:23 2010
New Revision: 988071

Add information about "||" and "|$" piped log
syntax to the docs.


Modified: httpd/httpd/trunk/docs/manual/logs.xml
--- httpd/httpd/trunk/docs/manual/logs.xml (original)
+++ httpd/httpd/trunk/docs/manual/logs.xml Mon Aug 23 11:13:23 2010
@@ -565,6 +565,24 @@
     <p>As with conditional logging, piped logs are a very powerful
     tool, but they should not be used where a simpler solution like
     off-line post-processing is available.</p>
+    <p>By default the piped log process is spawned without invoking
+    a shell. Use "<code>|$</code>" instead of "<code>|</code>"
+    to spawn using a shell (usually with <code>/bin/sh -c</code>):</p>
+    <example>
+      # Invoke "rotatelogs" using a shell
+      CustomLog "|$/usr/local/apache/bin/rotatelogs
+      /var/log/access_log 86400" common
+    </example>
+    <p>This was the default behaviour for Apache 2.2.
+    Depending on the shell specifics this might lead to
+    an additional shell process for the lifetime of the logging
+    pipe program and signal handling problems during restart.
+    For compatibility reasons with Apache 2.2 the notation
+    "<code>||</code>" is also supported and equivalent to using
+    "<code>|</code>".</p>
   <section id="virtualhost">

Modified: httpd/httpd/trunk/docs/manual/mod/core.xml
--- httpd/httpd/trunk/docs/manual/mod/core.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/core.xml Mon Aug 23 11:13:23 2010
@@ -993,13 +993,16 @@ in case of an error</description>
     <p>If the <var>file-path</var>
-    begins with a pipe (|) then it is assumed to be a command to spawn
-    to handle the error log.</p>
+    begins with a pipe character "<code>|</code>" then it is assumed to be a
+    command to spawn to handle the error log.</p>
     ErrorLog "|/usr/local/bin/httpd_errors"
+    <p>See the notes on <a href="../logs.html#piped">piped logs</a> for
+    more information.</p>
     <p>Using <code>syslog</code> instead of a filename enables logging
     via syslogd(8) if the system supports it. The default is to use
     syslog facility <code>local7</code>, but you can override this by

Modified: httpd/httpd/trunk/docs/manual/mod/mod_log_config.xml
--- httpd/httpd/trunk/docs/manual/mod/mod_log_config.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_log_config.xml Mon Aug 23 11:13:23 2010
@@ -391,7 +391,8 @@
       <dd>The pipe character "<code>|</code>", followed by the path
       to a program to receive the log information on its standard
-      input.
+      input. See the notes on <a href="../logs.html#piped">piped logs</a>
+      for more information.
       <note type="warning"><title>Security:</title>
       <p>If a program is used, then it will be run as the user who

View raw message