Roxen.git / server / base_server / configuration.pike

version» Context lines:

Roxen.git/server/base_server/configuration.pike:1:   // This file is part of Roxen WebServer.   // Copyright © 1996 - 2009, Roxen IS.   //      // @appears Configuration   //! A site's main configuration    - constant cvs_version = "$Id: configuration.pike,v 1.730 2012/11/12 09:23:26 jonasw Exp $"; + constant cvs_version = "$Id$";   #include <module.h>   #include <module_constants.h>   #include <roxen.h>   #include <request_trace.h>   #include <timers.h>      #define CATCH(P,X) do{mixed e;if(e=catch{X;})report_error("While "+P+"\n"+describe_backtrace(e));}while(0)      // Tell Pike.count_memory this is global.   constant pike_cycle_depth = 0;
Roxen.git/server/base_server/configuration.pike:4815:      <p>A line to format an event logging message is one of:</p>      <pre><i>&lt;facility&gt;</i>/<i>&lt;action&gt;</i>: <i>&lt;log format&gt;</i>   <i>&lt;facility&gt;</i>/*: <i>&lt;log format&gt;</i>   */*: <i>&lt;log format&gt;</i>   </pre>      <p><i>&lt;facility&gt;</i> matches an identifier for the Roxen module   or subsystem that the event comes from. Facility identifiers always - starts with a character in <code>[a-zA-Z0-9]</code> and contains only + start with a character in <code>[a-zA-Z0-9]</code> and contain only   characters in <code>[-_.#a-zA-Z0-9]</code>. If '<code>*</code>' is   used instead of <i>&lt;facility&gt;</i> then that line matches all   facilities that aren't matched by any other line.</p>      <p><i>&lt;action&gt;</i> matches an identifier for a specific kind of - event logged by a facility. An action identifier contains only + event logged by a facility. An action identifier may only contain   characters in <code>[-_.#a-zA-Z0-9]</code>. '<code>*</code>' may be   used instead of an <i>&lt;action&gt;</i> to match all events logged by   a facility that aren't matched by any other line.</p>      <p><i>&lt;log format&gt;</i> consists of literal characters and the   special specifiers described below. All specifiers are not applicable   for all kinds of messages. If an unknown or inapplicable specifier is   encountered it typically expands to '<code>-</code>', but in some   cases it expands to a dummy value that is syntactically compatible   with what it usually expands to.</p>      <p>For compatibility, underscores ('_') may be used wherever - hyphens ('-') occur in the specifier names.</p> + hyphens ('-') occur in the format specifier names.</p>      <h3>Format specifiers for both access and event logging</h3>      <table class='hilite-1stcol'><tbody valign='top'>   <tr><td>\\n \\t \\r</td>    <td>Insert a newline, tab or linefeed character, respectively.</td></tr>   <tr><td>$char(int)</td>    <td>Insert the (1 byte) character specified by the integer. E.g.    '<code>$char(36)</code>' inserts a literal '<code>$</code>'    character.</td></tr>   <tr><td>$wchar(int)</td>    <td>Insert the specified integer using 2 bytes in network byte -  order. Specify a negative integer to get the opposite (i.e. big +  order. Specify a negative integer to get the opposite (i.e. little    endian) order.</td></tr>   <tr><td>$int(int)</td>    <td>Insert the specified integer using 4 bytes in network byte -  order. Specify a negative integer to get the opposite (i.e. big +  order. Specify a negative integer to get the opposite (i.e. little    endian) order.</td></tr>   <tr><td>$^</td>    <td>Suppress newline at the end of the logentry.</td></tr>   <tr><td>$date</td>    <td>Local date formatted like '<code>2001-01-17</code>'.</td></tr>   <tr><td>$time</td>    <td>Local time formatted like '<code>13:00:00</code>'.</td></tr>   <tr><td>$cern-date</td>    <td>Local date and time in CERN Common Log file format, i.e.    like '<code>17/Jan/2001:13:00:00 +0200</code>'.</td></tr>   <tr><td>$utc-date</td>    <td>UTC date formatted like '<code>2001-01-17</code>'.</td></tr> -  +    <tr><td>$utc-time</td>    <td>UTC time formatted like '<code>13:00:00</code>'.</td></tr>   <tr><td>$bin-date</td>    <td>Unix time as a 32 bit integer in network byte order.</td></tr>   <tr><td>$resource</td>    <td>Resource identifier. For events, this is either a path to a    file (if it begins with '<code>/</code>') or some other kind of    resource identifier (otherwise). It is '-' for events that don't    act on any specific resource.</td></tr>   <tr><td>$server-uptime</td>    <td>Server uptime in seconds.</td></tr>   <tr><td>$server-cputime</td>    <td>Server cpu (user+system) time in milliseconds.</td></tr>   <tr><td>$server-usertime</td>    <td>Server cpu user time in milliseconds.</td></tr>   <tr><td>$server-systime</td>    <td>Server cpu system time in milliseconds.</td></tr>   </tbody></table>      <h3>Format specifiers for access logging</h3> -  + <p>Note that some of these may also be available +  for some event log actions</p>      <table class='hilite-1stcol'><tbody valign='top'>   <tr><td>$host</td>    <td>The remote host name, or ip number.</td></tr>   <tr><td>$vhost</td>    <td>The Host request-header sent by the client, or '-' if none.</td></tr>   <tr><td>$ip-number</td>    <td>The remote ip number.</td></tr>   <tr><td>$bin-ip-number</td>    <td>The remote host ip as a binary integer number.</td></tr>