Branch: Tag:

2009-12-05

2009-12-05 01:04:00 by 0

Localization.

Rev: server/base_server/global_variables.pike:1.123
Rev: server/config_interface/actions/cachestatus.pike:1.26
Rev: server/config_interface/actions/debug_info.pike:1.44
Rev: server/modules/security/userdb_sql.pike:1.12
Rev: server/translations/ces/admin_tasks.xml:1.32
Rev: server/translations/ces/roxen_config.xml:1.55
Rev: server/translations/ces/roxen_start.xml:1.2
Rev: server/translations/deu/admin_tasks.xml:1.32
Rev: server/translations/deu/roxen_config.xml:1.65
Rev: server/translations/deu/roxen_message.xml:1.18
Rev: server/translations/deu/roxen_start.xml:1.4
Rev: server/translations/eng/admin_tasks.xml:1.33
Rev: server/translations/eng/mod_userdb_sql.xml:1.3
Rev: server/translations/eng/roxen_config.xml:1.61
Rev: server/translations/eng/roxen_message.xml:1.28
Rev: server/translations/eng/roxen_start.xml:1.13
Rev: server/translations/hun/admin_tasks.xml:1.26
Rev: server/translations/hun/roxen_config.xml:1.51
Rev: server/translations/jpn/admin_tasks.xml:1.26
Rev: server/translations/jpn/roxen_config.xml:1.51
Rev: server/translations/nld/admin_tasks.xml:1.32
Rev: server/translations/nld/roxen_config.xml:1.56
Rev: server/translations/swe/admin_tasks.xml:1.31
Rev: server/translations/swe/roxen_config.xml:1.71
Rev: server/translations/swe/roxen_message.xml:1.30
Rev: server/translations/swe/roxen_start.xml:1.10

253:   <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 indentifier (otherwise).</td></tr> +  resource identifier (otherwise). It is '-' for events that doesn'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>
400:   below.</p>      <dl> +  + <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-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> +    <dt>Facility: sbfs</dt>    <dd><p>A SiteBuilder file system.</p>   
3499:   <o>Are you sure you want to restore the default value?</o>   <t></t>   </str> +  + <str id="1043"> + <o>Cache: Memory cache size</o> + <t></t> + </str> +  + <str id="1044"> + <o>&lt;p&gt;Maximum size in MByte for all RAM caches taken together. This limit + covers the caches visible in the &lt;a + href='/actions/?action=cachestatus.pike&amp;class=status'&gt;Cache status&lt;/a&gt; + page.&lt;/p&gt; +  + &lt;p&gt;Note that there are many more things in the Roxen WebServer that + take space, including some caches that are not handled by the common + RAM cache. Also, there is various indirect memory overhead that is not + directly accounted for by the size calculations. All these taken + together means that the figure configured here cannot be mapped + straightly to the size of the Roxen process as reported by the OS. The + optimal setting here is the one that in general keeps the Roxen + process at a size that avoids swapping and leaves enough memory for + buffers and other processes that need to run at the same time (e.g. + the Roxen instance of the MySQL server).&lt;/p&gt;</o> + <t></t> + </str> +  + <str id="1045"> + <o>Cache: Memory cache GC interval</o> + <t></t> + </str> +  + <str id="1046"> + <o>&lt;p&gt;Interval in seconds between RAM cache garbage collector runs. This + GC removes entries from the RAM caches that have timed out or are + stale for other reasons, thereby making more room for new entries. The + configured cache size limits are enforced when entries are added, so + this GC is not required to keep the cache sizes down.&lt;/p&gt; +  + &lt;p&gt;Running this GC too seldom causes some RAM caches to contain many + invalid cache entries, which could push out valid cache entries. + Running it too often causes unnecessary server load.&lt;/p&gt;</o> + <t></t> + </str>