Document syslogd-based error logging

<A

 HREF="directive-dict.html#Syntax"

 REL="Help"

><STRONG>Syntax:</STRONG></A> ErrorLog <EM>filename</EM><BR>

><STRONG>Syntax:</STRONG></A> ErrorLog <EM>filename</EM>|<CODE>syslog</CODE><BR>

<A

 HREF="directive-dict.html#Default"

 REL="Help"

then it is assumed to be relative to the <A HREF="#serverroot">ServerRoot</A>.

If the filename begins with a pipe (|) then it is assumed to be a command to

spawn to handle the error log.

<p>

Example:

<BLOCKQUOTE><CODE>ErrorLog /dev/null</CODE></BLOCKQUOTE>

This effectively turns off error logging.<P>

<P><STRONG>Apache 1.3 and above:</STRONG>

Using <CODE>syslog</CODE> instead of a filename enables logging via syslogd(8)

if the system supports it.

<P>

SECURITY: See the <A HREF="../misc/security_tips.html#serverroot">security tips</A>

document for details on why your security could be compromised if

the directory where logfiles are stored is writable by anyone other

than the user that starts the server.

<P><STRONG>See also:</STRONG> <A HREF="#loglevel">LogLevel</A>

<P><HR>

<H2><A name="files">&lt;Files&gt; directive</A></H2>

><STRONG>Compatibility:</STRONG></A> LogLevel is only available in 1.3 or later.

<P>LogLevel adjusts the verbosity of the messages recorded in the

error logs.  The following <EM>level</EM>s are available, in order of

error logs (see <A HREF="#errorlog">ErrorLog</A> directive).

The following <EM>level</EM>s are available, in order of

decreasing significance:

<P><TABLE>

of higher significance will be reported as well.  E.g., when 

<CODE>LogLevel info</CODE> is specified, then messages with log levels of

<CODE>notice</CODE> and <CODE>warn</CODE> will also be posted.

<P>

Using a level of at least <CODE>crit</CODE> is recommended.

<P><HR>

<H2><A name="maxclients">MaxClients directive</A></H2>