httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From br...@hyperreal.org
Subject cvs commit: apache-1.3/htdocs/manual/mod core.html
Date Sat, 07 Feb 1998 00:24:42 GMT
brian       98/02/06 16:24:42

  Modified:    htdocs/manual/mod core.html
  Log:
  Playing whack-a-mole; first stab at docs for LogLevel.  Could someone confirm?
  
  Revision  Changes    Path
  1.98      +64 -0     apache-1.3/htdocs/manual/mod/core.html
  
  Index: core.html
  ===================================================================
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/mod/core.html,v
  retrieving revision 1.97
  retrieving revision 1.98
  diff -u -r1.97 -r1.98
  --- core.html	1998/02/05 20:04:34	1.97
  +++ core.html	1998/02/07 00:24:40	1.98
  @@ -52,6 +52,7 @@
   <LI><A HREF="#location">&lt;Location&gt;</A>
   <LI><A HREF="#locationmatch">&lt;LocationMatch&gt;</A>
   <LI><A HREF="#lockfile">LockFile</A>
  +<LI><A HREF="#loglevel">LogLevel</A>
   <LI><A HREF="#maxclients">MaxClients</A>
   <LI><A HREF="#maxkeepaliverequests">MaxKeepAliveRequests</A>
   <LI><A HREF="#maxrequestsperchild">MaxRequestsPerChild</A>
  @@ -1426,6 +1427,69 @@
   could create a denial of service attack and prevent the server from
   starting by creating a lockfile with the same name as the one the 
   server will try to create.<P>
  +
  +<P><HR>
  +
  +<H2><A NAME="loglevel">LogLevel directive</A></H2>
  +<A
  + HREF="directive-dict.html#Syntax"
  + REL="Help"
  +><STRONG>Syntax:</STRONG></A> LogLevel <EM>level</EM><BR>
  +<A
  + HREF="directive-dict.html#Default"
  + REL="Help"
  +><STRONG>Default:</STRONG></A> <CODE>LogLevel error</CODE><BR>
  +<A
  + HREF="directive-dict.html#Context"
  + REL="Help"
  +><STRONG>Context:</STRONG></A> server config, virtual host<BR>
  +<A
  + HREF="directive-dict.html#Status"
  + REL="Help"
  +><STRONG>Status:</STRONG></A> core<BR>
  +<A
  + HREF="directive-dict.html#Compatibility"
  + REL="Help"
  +><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
  +decreasing significance:
  +
  +<P><TABLE>
  +  <TR><TH ALIGN="LEFT"><STRONG>Level</STRONG>
  +      <TH ALIGN="LEFT"><STRONG>Description</STRONG>
  +  <TR><TH><TH ALIGN="LEFT"><STRONG>Example</STRONG>
  +  <TR><TD><CODE>emerg</CODE>
  +      <TD>Emergencies - system is unusable.
  +  <TR><TD><TD>"Child cannot open lock file.  Exiting"    
  +  <TR><TD><CODE>alert</CODE>
  +      <TD>Action must be taken immediately.
  +  <TR><TD><TD>"getpwuid: couldn't determine user name from uid"
  +  <TR><TD><CODE>crit</CODE>
  +      <TD>Critical Conditions.
  +  <TR><TD><TD>"socket: Failed to get a socket, exiting child"
  +  <TR><TD><CODE>error</CODE>
  +      <TD>Error conditions.
  +  <TR><TD><TD>"Premature end of script headers"
  +  <TR><TD><CODE>warn</CODE>
  +      <TD>Warning conditions.
  +  <TR><TD><TD>"request lost connection to xxx.yyy.zzz.aaa"
  +  <TR><TD><CODE>notice</CODE>
  +      <TD>Normal but significant condition.
  +  <TR><TD><TD>"httpd: caught SIGBUS, attempting to dump core in ..."
  +  <TR><TD><CODE>info</CODE>
  +      <TD>Informational.
  +  <TR><TD><TD>"Server seems busy, (you may need to increase StartServers,
or Min/MaxSpareServers)..."
  +  <TR><TD><CODE>debug</CODE>
  +      <TD>Debug-level messages
  +  <TR><TD><TD>"Opening config file ..."
  +</TABLE>
  +
  +<P>When a particular level is specified, messages from all other levels
  +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><HR>
   
  
  
  

Mime
View raw message