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.687 2009/11/12 14:43:59 mast Exp $"; + constant cvs_version = "$Id: configuration.pike,v 1.688 2009/11/27 13:37:53 mast Exp $";   #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:4823:   #ifdef NEW_RAM_CACHE    #"\n   <dt>Facility: roxen</dt>    <dd><p>This is logging for systems in the Roxen WebServer core.    For logging that is not related to any specific configuration, the    configuration for the Administration Interface is used.</p>       <p>The known events are:</p>       <table><tbody valign='top'> -  <tr><td>ram-gc</td> +  <tr><td>ram-cache-gc</td>    <td>Logged after the RAM cache GC has run. $handle-time and    $handle-cputime are set to the time the GC took (see    descriptions above for details).</td></tr> -  +  <tr><td>ram-cache-rebase</td> +  <td>Logged when the RAM cache has performed a rebias of the +  priority queue values. Is a problem only if it starts to +  happen too often.</td></tr>    </tbody></table></dd>"   #endif    #"\n   <dt>Facility: sbfs</dt>    <dd><p>A SiteBuilder file system.</p>       <p>The actions <code>commit</code>, <code>purge</code>,    <code>mkdir</code>, <code>set-dir-md</code>, and    <code>rmdir</code> are logged for file system changes except those    in edit areas.</p>