Branch: Tag:

2009-12-05

2009-12-05 01:04:00 by Jonas Wallden <jonasw@roxen.com>

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

402:   </str>      <str id="68"> - <o>supportdb</o> + <o>Supports database</o>   <t></t>   </str>   
1363:   <o>Click on a Patch for more information.</o>   <t></t>   </str> +  + <str id="380"> + <o>Configure cache settings</o> + <t></t> + </str> +  + <str id="381"> + <o>The configured maximum size %s is divided dynamically between the + cache managers based on the usage for the last half hour. If the + caches are not full then all free space is assigned to each one of + them. They will shrink to the configured maximum size as they fill up.</o> + <t></t> + </str> +  + <str id="382"> + <o>Cache manager</o> + <t></t> + </str> +  + <str id="383"> + <o>Size limit</o> + <t></t> + </str> +  + <str id="384"> + <o>Input rate</o> + <t></t> + </str> +  + <str id="385"> + <o>Cost HR</o> + <t></t> + </str> +  + <str id="386"> + <o>Cache manager: </o> + <t></t> + </str> +  + <str id="387"> + <o>Lookups</o> + <t></t> + </str> +  + <str id="388"> + <o>Size/entry</o> + <t></t> + </str> +  + <str id="389"> + <o>Byte HR</o> + <t></t> + </str> +  + <str id="390"> + <o>Create cost</o> + <t></t> + </str> +  + <str id="391"> + <o>Cost/entry</o> + <t></t> + </str> +  + <str id="392"> + <o>&lt;i&gt;Cost HR&lt;/i&gt; is the cost hit rate, i.e. every hit and miss is + weighted with the cost for each entry according to the cost metric of + the cache manager. Note that it uses the approximation that every + cache miss is followed by the addition of a new cache entry.</o> + <t></t> + </str> +  + <str id="393"> + <o>Garbage Collector</o> + <t></t> + </str> +  + <str id="394"> + <o>The garbage collector has not run yet.</o> + <t></t> + </str> +  + <str id="395"> + <o>%d seconds since the last garbage collection. The following statistics are over approximately the last hour.</o> + <t></t> + </str> +  + <str id="396"> + <o>Time spent in the garbage collector:</o> + <t></t> + </str> +  + <str id="397"> + <o>Size of garbage collected entries:</o> + <t></t> + </str> +  + <str id="398"> + <o>stale</o> + <t></t> + </str> +  + <str id="399"> + <o>timed out</o> + <t></t> + </str> +  + <str id="400"> + <o>Garbage collection ratio:</o> + <t></t> + </str> +  + <str id="401"> + <o>Note that the garbage collector referred to here is not the same as + the one for the &lt;a + href='/actions/?action=cachestatus.pike&amp;class=status'&gt;Roxen memory + cache&lt;/a&gt;. This is the low-level garbage collector used internally by + the Pike interpreter.</o> + <t></t> + </str> +  + <str id="402"> + <o>Cache</o> + <t></t> + </str>