You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by rb...@apache.org on 2002/10/28 02:52:01 UTC
cvs commit: httpd-2.0/docs/manual/mod core.html.en core.xml
rbowen 2002/10/27 17:52:01
Modified: docs/manual/mod core.html.en core.xml
Log:
Add examples of using ErrorLog, particularly logging to syslog.
Revision Changes Path
1.40 +15 -1 httpd-2.0/docs/manual/mod/core.html.en
Index: core.html.en
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/mod/core.html.en,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- core.html.en 15 Oct 2002 03:30:17 -0000 1.39
+++ core.html.en 28 Oct 2002 01:52:01 -0000 1.40
@@ -759,16 +759,30 @@
<p>The <code class="directive">ErrorLog</code> directive sets the name of
the file to which the server will log any errors it encounters. If
the <var>file-path</var> does not begin with a slash (/) then it is
- assumed to be relative to the <code class="directive"><a href="#serverroot">ServerRoot</a></code>. If the <var>file-path</var>
+ assumed to be relative to the <code class="directive"><a href="#serverroot">ServerRoot</a></code>.</p>
+
+ <div class="example"><h3>Example</h3><p><code>
+ ErrorLog /var/log/httpd/error_log
+ </code></p></div>
+
+ <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>
+ <div class="example"><h3>Example</h3><p><code>
+ ErrorLog "|/usr/local/bin/httpd_errors"
+ </code></p></div>
+
<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
using the <code>syslog:<var>facility</var></code> syntax where
<var>facility</var> can be one of the names usually documented in
syslog(1).</p>
+
+ <div class="example"><h3>Example</h3><p><code>
+ ErrorLog syslog:user
+ </code></p></div>
<p>SECURITY: See the <a href="../misc/security_tips.html#serverroot">security tips</a>
document for details on why your security could be compromised
1.39 +15 -1 httpd-2.0/docs/manual/mod/core.xml
Index: core.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/mod/core.xml,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -r1.38 -r1.39
--- core.xml 15 Oct 2002 03:30:17 -0000 1.38
+++ core.xml 28 Oct 2002 01:52:01 -0000 1.39
@@ -851,16 +851,30 @@
the file to which the server will log any errors it encounters. If
the <var>file-path</var> does not begin with a slash (/) then it is
assumed to be relative to the <directive
- module="core">ServerRoot</directive>. If the <var>file-path</var>
+ module="core">ServerRoot</directive>.</p>
+
+ <example><title>Example</title>
+ ErrorLog /var/log/httpd/error_log
+ </example>
+
+ <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>
+ <example><title>Example</title>
+ ErrorLog "|/usr/local/bin/httpd_errors"
+ </example>
+
<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
using the <code>syslog:<var>facility</var></code> syntax where
<var>facility</var> can be one of the names usually documented in
syslog(1).</p>
+
+ <example><title>Example</title>
+ ErrorLog syslog:user
+ </example>
<p>SECURITY: See the <a
href="../misc/security_tips.html#serverroot">security tips</a>