Roxen.git / server / translations / eng / roxen_config.xml

version» Context lines:

Roxen.git/server/translations/eng/roxen_config.xml:7:   <file>../base_server/global_variables.pike</file>   <file>../base_server/module_support.pike</file>   <file>../config_interface/actions/index.html</file>   <file>../config_interface/boxes/Box.pmod</file>   <file>../config_interface/boxes/articles.pike</file>   <file>../config_interface/boxes/crunch.pike</file>   <file>../config_interface/boxes/doclinks.pike</file>   <file>../config_interface/boxes/megatokyo.pike</file>   <file>../config_interface/boxes/ris_news.pike</file>   <file>../config_interface/boxes/server_status.pike</file> + <file>../config_interface/boxes/snmp_status.pike</file>   <file>../config_interface/boxes/welcome.pike</file>   <file>../config_interface/cv_startpage_tabs.pike</file>   <file>../config_interface/dbs/backups.html</file>   <file>../config_interface/dbs/browser.pike</file>   <file>../config_interface/dbs/create_db.html</file>   <file>../config_interface/dbs/create_group.html</file>   <file>../config_interface/dbs/db_list.pike</file>   <file>../config_interface/dbs/db_maintenance.pike</file>   <file>../config_interface/dbs/db_matrix.pike</file>   <file>../config_interface/dbs/db_optimizeall.html</file>
Roxen.git/server/translations/eng/roxen_config.xml:212:   for all kinds of messages. If an unknown or inapplicable specifier is   encountered it typically expands to '&lt;code&gt;-&lt;/code&gt;', but in some   cases it expands to a dummy value that is syntactically compatible   with what it usually expands to.&lt;/p&gt;      &lt;p&gt;For compatibility, underscores ('_') may be used wherever   hyphens ('-') occur in the specifier names.&lt;/p&gt;      &lt;h3&gt;Format specifiers for both access and event logging&lt;/h3&gt;    - &lt;table&gt;&lt;tbody valign='top'&gt; + &lt;table class='hilite-1stcol'&gt;&lt;tbody valign='top'&gt;   &lt;tr&gt;&lt;td&gt;\n \t \r&lt;/td&gt;    &lt;td&gt;Insert a newline, tab or linefeed character, respectively.&lt;/td&gt;&lt;/tr&gt;   &lt;tr&gt;&lt;td&gt;$char(int)&lt;/td&gt;    &lt;td&gt;Insert the (1 byte) character specified by the integer. E.g.    '&lt;code&gt;$char(36)&lt;/code&gt;' inserts a literal '&lt;code&gt;$&lt;/code&gt;'    character.&lt;/td&gt;&lt;/tr&gt;   &lt;tr&gt;&lt;td&gt;$wchar(int)&lt;/td&gt;    &lt;td&gt;Insert the specified integer using 2 bytes in network byte    order. Specify a negative integer to get the opposite (i.e. big    endian) order.&lt;/td&gt;&lt;/tr&gt;
Roxen.git/server/translations/eng/roxen_config.xml:246:   &lt;tr&gt;&lt;td&gt;$utc-date&lt;/td&gt;    &lt;td&gt;UTC date formatted like '&lt;code&gt;2001-01-17&lt;/code&gt;'.&lt;/td&gt;&lt;/tr&gt;      &lt;tr&gt;&lt;td&gt;$utc-time&lt;/td&gt;    &lt;td&gt;UTC time formatted like '&lt;code&gt;13:00:00&lt;/code&gt;'.&lt;/td&gt;&lt;/tr&gt;   &lt;tr&gt;&lt;td&gt;$bin-date&lt;/td&gt;    &lt;td&gt;Unix time as a 32 bit integer in network byte order.&lt;/td&gt;&lt;/tr&gt;   &lt;tr&gt;&lt;td&gt;$resource&lt;/td&gt;    &lt;td&gt;Resource identifier. For events, this is either a path to a    file (if it begins with '&lt;code&gt;/&lt;/code&gt;') or some other kind of -  resource identifier (otherwise). It is '-' for events that doesn't +  resource identifier (otherwise). It is '-' for events that don't    act on any specific resource.&lt;/td&gt;&lt;/tr&gt;   &lt;tr&gt;&lt;td&gt;$server-uptime&lt;/td&gt;    &lt;td&gt;Server uptime in seconds.&lt;/td&gt;&lt;/tr&gt;   &lt;tr&gt;&lt;td&gt;$server-cputime&lt;/td&gt;    &lt;td&gt;Server cpu (user+system) time in milliseconds.&lt;/td&gt;&lt;/tr&gt;   &lt;tr&gt;&lt;td&gt;$server-usertime&lt;/td&gt;    &lt;td&gt;Server cpu user time in milliseconds.&lt;/td&gt;&lt;/tr&gt;   &lt;tr&gt;&lt;td&gt;$server-systime&lt;/td&gt;    &lt;td&gt;Server cpu system time in milliseconds.&lt;/td&gt;&lt;/tr&gt;   &lt;/tbody&gt;&lt;/table&gt;      &lt;h3&gt;Format specifiers for access logging&lt;/h3&gt;    - &lt;table&gt;&lt;tbody valign='top'&gt; + &lt;table class='hilite-1stcol'&gt;&lt;tbody valign='top'&gt;   &lt;tr&gt;&lt;td&gt;$host&lt;/td&gt;    &lt;td&gt;The remote host name, or ip number.&lt;/td&gt;&lt;/tr&gt;   &lt;tr&gt;&lt;td&gt;$vhost&lt;/td&gt;    &lt;td&gt;The Host request-header sent by the client, or '-' if none.&lt;/td&gt;&lt;/tr&gt;   &lt;tr&gt;&lt;td&gt;$ip-number&lt;/td&gt;    &lt;td&gt;The remote ip number.&lt;/td&gt;&lt;/tr&gt;   &lt;tr&gt;&lt;td&gt;$bin-ip-number&lt;/td&gt;    &lt;td&gt;The remote host ip as a binary integer number.&lt;/td&gt;&lt;/tr&gt;   &lt;tr&gt;&lt;td&gt;$xff&lt;/td&gt;    &lt;td&gt;The remote host name/ip taken from the X-Forwarded-For header, or
Roxen.git/server/translations/eng/roxen_config.xml:343:    otherwise '0'.&lt;/td&gt;&lt;/tr&gt;   &lt;tr&gt;&lt;td&gt;$content-type&lt;/td&gt;    &lt;td&gt;Resource MIME type.&lt;/td&gt;&lt;/tr&gt;   &lt;tr&gt;&lt;td&gt;$cookies&lt;/td&gt;    &lt;td&gt;All cookies sent by the browser, separated by ';'.&lt;/td&gt;&lt;/tr&gt;      &lt;tr&gt;&lt;td&gt;$cache-status&lt;/td&gt;    &lt;td&gt;A comma separated list of words (containing no whitespace)    that describes how the request got handled by various caches:    -  &lt;table&gt;&lt;tbody valign='top'&gt; +  &lt;table class='hilite-1stcol'&gt;&lt;tbody valign='top'&gt;    &lt;tr&gt;&lt;td&gt;protcache&lt;/td&gt;    &lt;td&gt;The page is served from the HTTP protocol cache.&lt;/td&gt;&lt;/tr&gt;    &lt;tr&gt;&lt;td&gt;protstore&lt;/td&gt;    &lt;td&gt;The page is stored in the HTTP protocol cache.&lt;/td&gt;&lt;/tr&gt;    &lt;tr&gt;&lt;td&gt;stale&lt;/td&gt;    &lt;td&gt;There is a stale entry in the HTTP protocol cache. A    refresh is underway in the background and the stale entry is    sent in the meantime to avoid a long response time and server    congestion.&lt;/td&gt;&lt;/tr&gt;    &lt;tr&gt;&lt;td&gt;refresh&lt;/td&gt;    &lt;td&gt;This is the finishing of the background refresh request    for the entry in the HTTP protocol cache.&lt;/td&gt;&lt;/tr&gt; -  +  &lt;tr&gt;&lt;td&gt;icachedraw&lt;/td&gt; +  &lt;td&gt;A server-generated image had to be rendered from scratch.&lt;/td&gt;&lt;/tr&gt; +  &lt;tr&gt;&lt;td&gt;icacheram&lt;/td&gt; +  &lt;td&gt;A server-generated image was found in the RAM cache.&lt;/td&gt;&lt;/tr&gt; +  &lt;tr&gt;&lt;td&gt;icachedisk&lt;/td&gt; +  &lt;td&gt;A server-generated image was found in the disk cache (i.e. in +  the server's MySQL database).&lt;/td&gt;&lt;/tr&gt;    &lt;tr&gt;&lt;td&gt;pcoderam&lt;/td&gt;    &lt;td&gt;A hit in the RXML p-code RAM cache.&lt;/td&gt;&lt;/tr&gt;    &lt;tr&gt;&lt;td&gt;pcodedisk&lt;/td&gt;    &lt;td&gt;A hit in the RXML p-code persistent cache.&lt;/td&gt;&lt;/tr&gt; -  +  &lt;tr&gt;&lt;td&gt;pcodestore&lt;/td&gt; +  &lt;td&gt;P-code is added to or updated in the persistent cache.&lt;/td&gt;&lt;/tr&gt; +  &lt;tr&gt;&lt;td&gt;pcodestorefailed&lt;/td&gt; +  &lt;td&gt;An attempt to add or update p-code in the persistent cache +  failed (e.g. due to a race with another request).&lt;/td&gt;&lt;/tr&gt;    &lt;tr&gt;&lt;td&gt;cachetag&lt;/td&gt;    &lt;td&gt;RXML was evaluated without any cache miss in any RXML    &amp;lt;cache&amp;gt; tag. The &amp;lt;nocache&amp;gt; tag does not count as a    miss.&lt;/td&gt;&lt;/tr&gt;    &lt;tr&gt;&lt;td&gt;xsltcache&lt;/td&gt;    &lt;td&gt;There is a hit XSLT cache.&lt;/td&gt;&lt;/tr&gt;    &lt;tr&gt;&lt;td&gt;nocache&lt;/td&gt;    &lt;td&gt;No hit in any known cache, and not added to the HTTP    protocol cache.&lt;/td&gt;&lt;/tr&gt;    &lt;/tbody&gt;&lt;/table&gt;&lt;/td&gt;&lt;/tr&gt;      &lt;tr&gt;&lt;td&gt;$eval-status&lt;/td&gt;    &lt;td&gt;A comma separated list of words (containing no whitespace)    that describes how the page has been evaluated:    -  &lt;table&gt;&lt;tbody valign='top'&gt; +  &lt;table class='hilite-1stcol'&gt;&lt;tbody valign='top'&gt;    &lt;tr&gt;&lt;td&gt;xslt&lt;/td&gt;    &lt;td&gt;XSL transform.&lt;/td&gt;&lt;/tr&gt;    &lt;tr&gt;&lt;td&gt;rxmlsrc&lt;/td&gt;    &lt;td&gt;RXML evaluated from source.&lt;/td&gt;&lt;/tr&gt;    &lt;tr&gt;&lt;td&gt;rxmlpcode&lt;/td&gt;    &lt;td&gt;RXML evaluated from compiled p-code.&lt;/td&gt;&lt;/tr&gt;    &lt;/tbody&gt;&lt;/table&gt;&lt;/td&gt;&lt;/tr&gt;      &lt;tr&gt;&lt;td&gt;$protcache-cost&lt;/td&gt;    &lt;td&gt;The lookup depth in the HTTP protocol module low-level cache.&lt;/td&gt;&lt;/tr&gt;   &lt;/tbody&gt;&lt;/table&gt;      &lt;h3&gt;Event logging&lt;/h3&gt;      &lt;p&gt;The known event logging facilities and modules are described   below.&lt;/p&gt;      &lt;dl&gt; -  +    &lt;dt&gt;Facility: roxen&lt;/dt&gt;    &lt;dd&gt;&lt;p&gt;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.&lt;/p&gt;       &lt;p&gt;The known events are:&lt;/p&gt;    -  &lt;table&gt;&lt;tbody valign='top'&gt; +  &lt;table class='hilite-1stcol'&gt;&lt;tbody valign='top'&gt;    &lt;tr&gt;&lt;td&gt;ram-cache-gc&lt;/td&gt;    &lt;td&gt;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).&lt;/td&gt;&lt;/tr&gt;    &lt;tr&gt;&lt;td&gt;ram-cache-rebase&lt;/td&gt;    &lt;td&gt;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.&lt;/td&gt;&lt;/tr&gt;    &lt;/tbody&gt;&lt;/table&gt;&lt;/dd&gt;   
Roxen.git/server/translations/eng/roxen_config.xml:430:       &lt;p&gt;The action &lt;code&gt;crawl-file&lt;/code&gt; is logged for files that are    crawled by the persistent cache crawler.&lt;/p&gt;       &lt;p&gt;The actions &lt;code&gt;file-change&lt;/code&gt; and    &lt;code&gt;dir-change-flat&lt;/code&gt; are logged when external file and    directory changes are detected (and this feature is enabled).&lt;/p&gt;       &lt;p&gt;These extra format specifiers are defined where applicable:&lt;/p&gt;    -  &lt;table&gt;&lt;tbody valign='top'&gt; +  &lt;table class='hilite-1stcol'&gt;&lt;tbody valign='top'&gt;    &lt;tr&gt;&lt;td&gt;$ac-userid&lt;/td&gt;    &lt;td&gt;The ID number of the AC identity whose edit area was used.    Zero for the common view area.&lt;/td&gt;&lt;/tr&gt;    &lt;tr&gt;&lt;td&gt;$workarea&lt;/td&gt;    &lt;td&gt;The unique tag for the work area. Empty for the main work    area.&lt;/td&gt;&lt;/tr&gt;    &lt;tr&gt;&lt;td&gt;$commit-type&lt;/td&gt;    &lt;td&gt;The type of file commit, one of &lt;code&gt;create&lt;/code&gt;,    &lt;code&gt;edit&lt;/code&gt;, &lt;code&gt;delete&lt;/code&gt;, and    &lt;code&gt;undelete&lt;/code&gt;.&lt;/td&gt;&lt;/tr&gt;
Roxen.git/server/translations/eng/roxen_config.xml:473:   <o>Log requests</o>   <t></t>   </str>      <str id="30">   <o>Logging: Log file</o>   <t></t>   </str>      <str id="31"> - <o>The log file. &lt;pre&gt;%y Year (e.g. '1997') + <o>The log file. A file name. Some substitutions will be done:&lt;pre&gt;%y Year (e.g. '1997')   %m Month (e.g. '08')   %d Date (e.g. '10' for the tenth)   %h Hour (e.g. '00')   %H Hostname   &lt;/pre&gt;</o>   <t></t>   </str>      <str id="32">   <o>Logging: No Logging for</o>
Roxen.git/server/translations/eng/roxen_config.xml:1095:   <str id="160">   <o>Auto Restart: Enable Automatic Restart</o>   <t></t>   </str>      <str id="161">   <o>If set, Roxen will automatically restart after a configurable number of days. Since Roxen uses a monolith, non-forking server model the process tends to grow in size over time. This is mainly due to heap fragmentation but may also sometimes be because of memory leaks.</o>   <t></t>   </str>    - <str id="170"> - <o>Cache: Memory Cache Garbage Collect Interval</o> - <t></t> - </str> -  - <str id="171"> - <o>The number of seconds between every garbage collect (removal of old content) from the memory cache. The memory cache is used for various tasks like remembering what supports flags matches what client.</o> - <t></t> - </str> -  +    <str id="172">   <o>Commented config files</o>   <t></t>   </str>      <str id="173">   <o>Save the variable documentation strings as comments in the configuration files. Only useful if you read or edit the config files directly.</o>   <t></t>   </str>   
Roxen.git/server/translations/eng/roxen_config.xml:1623:   </str>      <str id="304">   <o>If true, tasks are grouped acording to type, otherwise all tasks will be listed on one page</o>   <t></t>   </str>      <str id="305">   <o>The modules security level is used to determine if a request should be handled by the module.   &lt;p&gt;&lt;h2&gt;Security level vs Trust level&lt;/h2&gt; Each module has a configurable &lt;i&gt;security level&lt;/i&gt;. Each request has an assigned trust level. Higher &lt;i&gt;trust levels&lt;/i&gt; grants access to modules with higher &lt;i&gt;security levels&lt;/i&gt;. - &lt;p&gt;&lt;h2&gt;Definitions&lt;/h2&gt;&lt;ul&gt; &lt;li&gt;A requests initial Trust level is infinitely high.&lt;/li&gt; &lt;li&gt; A request will only be handled by a module if its &lt;i&gt;trust level&lt;/i&gt; is higher or equal to the &lt;i&gt;security level&lt;/i&gt; of the module.&lt;/li&gt; &lt;li&gt; Each time the request is handled by a module the &lt;i&gt;trust level&lt;/i&gt; of the module will be set to the lower of its &lt;i&gt;trust level&lt;/i&gt; and the modules &lt;i&gt;security level&lt;/i&gt;, &lt;i&gt;unless&lt;/i&gt; the security level of the module is 0, which is a special case and means that no change should be made.&lt;/li&gt; &lt;/ul&gt;&lt;/p&gt; + &lt;p&gt;&lt;h2&gt;Definitions&lt;/h2&gt;&lt;ul&gt; &lt;li&gt;A requests initial trust level is infinitely high.&lt;/li&gt; &lt;li&gt; A request will only be handled by a module if its &lt;i&gt;trust level&lt;/i&gt; is higher or equal to the &lt;i&gt;security level&lt;/i&gt; of the module.&lt;/li&gt; &lt;li&gt; Each time the request is handled by a module the &lt;i&gt;trust level&lt;/i&gt; of the request will be set to the lower of its &lt;i&gt;trust level&lt;/i&gt; and the modules &lt;i&gt;security level&lt;/i&gt;, &lt;i&gt;unless&lt;/i&gt; the security level of the module is 0, which is a special case and means that no change should be made.&lt;/li&gt; &lt;/ul&gt;&lt;/p&gt;   &lt;p&gt;&lt;h2&gt;Example&lt;/h2&gt; Modules:&lt;ul&gt; &lt;li&gt; User filesystem, &lt;i&gt;security level&lt;/i&gt; 1&lt;/li&gt; &lt;li&gt; Filesystem module, &lt;i&gt;security level&lt;/i&gt; 3&lt;/li&gt; &lt;li&gt; CGI module, &lt;i&gt;security level&lt;/i&gt; 2&lt;/li&gt; &lt;/ul&gt;&lt;/p&gt;   &lt;p&gt;A request handled by "User filesystem" is assigned a &lt;i&gt;trust level&lt;/i&gt; of one after the &lt;i&gt;security level&lt;/i&gt; of that module. That request can then not be handled by the "CGI module" since that module has a higher &lt;i&gt;security level&lt;/i&gt; than the requests trust level.&lt;/p&gt; - &lt;p&gt;On the other hand, a request handled by the the "Filsystem module" could later be handled by the "CGI module".&lt;/p&gt;</o> + &lt;p&gt;On the other hand, a request handled by the the "Filesystem module" could later be handled by the "CGI module".&lt;/p&gt;</o>   <t></t>   </str>      <str id="306">   <o>Site</o>   <t></t>   </str>      <str id="307">   <o>No such file message override files</o>
Roxen.git/server/translations/eng/roxen_config.xml:2112:   <str id="378">   <o>Reset query</o>   <t></t>   </str>      <str id="379">   <o>Run query</o>   <t></t>   </str>    - <str id="380"> - <o>While running %s: %s</o> - <t></t> - </str> -  +    <str id="382">   <o>Failed to enable %s</o>   <t></t>   </str>      <str id="383">   <o>Documentation</o>   <t></t>   </str>   
Roxen.git/server/translations/eng/roxen_config.xml:2143:   &lt;dd&gt;Select a non-default authentication method.&lt;/dd&gt;&lt;dt&gt;&lt;b&gt;realm&lt;/b&gt; &lt;i&gt;realm name&lt;/i&gt;&lt;/dt&gt;   &lt;dd&gt;The realm is used when user authentication info is requested&lt;/dd&gt;&lt;/dl&gt;    Below, CMD is one of 'allow' and 'deny'    &lt;dl&gt;    &lt;dt&gt;CMD &lt;b&gt;ip&lt;/b&gt;=&lt;i&gt;ip/bits&lt;/i&gt; [return]&lt;br /&gt;    CMD &lt;b&gt;ip&lt;/b&gt;=&lt;i&gt;ip:mask&lt;/i&gt; [return] &lt;br /&gt;    CMD &lt;b&gt;ip&lt;/b&gt;=&lt;i&gt;pattern[,pattern,...]&lt;/i&gt; [return] &lt;br /&gt;&lt;/dt&gt;    &lt;dd&gt;Match the remote IP-address.&lt;/dd&gt;       &lt;dt&gt;CMD &lt;b&gt;user&lt;/b&gt;=&lt;i&gt;name[,name,...]&lt;/i&gt; [return]&lt;/dt&gt; -  &lt;dd&gt;Requires a authenticated user. If the user name 'any' is used, any valid user will be OK. Otherwise, one of the listed users are required.&lt;/dd&gt; &lt;dt&gt;CMD &lt;b&gt;group&lt;/b&gt;=&lt;i&gt;name[,name,...]&lt;/i&gt; [return]&lt;/dt&gt; - &lt;dd&gt;Requires a authenticated user with a group. If the group name 'any' is used, any valid group will be OK. Otherwise, one of the listed groups are required.&lt;/dd&gt; +  &lt;dd&gt;Requires an authenticated user. If the user name 'any' is used, any valid user will be OK; if the user name 'ANY' is used, a valid user is preferred, but not required. Otherwise, one of the listed users is required.&lt;/dd&gt; &lt;dt&gt;CMD &lt;b&gt;group&lt;/b&gt;=&lt;i&gt;name[,name,...]&lt;/i&gt; [return]&lt;/dt&gt; + &lt;dd&gt;Requires an authenticated user with a group. If the group name 'any' is used, any valid group will be OK. Otherwise, one of the listed groups are required.&lt;/dd&gt;      &lt;dt&gt;CMD &lt;b&gt;dns&lt;/b&gt;=&lt;i&gt;pattern[,pattern,...]&lt;/i&gt; [return]&lt;/dt&gt;   &lt;dd&gt;Require one of the specified DNS domain-names&lt;/dd&gt;   &lt;dt&gt;CMD &lt;b&gt;time&lt;/b&gt;=&lt;i&gt;HH:mm-HH:mm&lt;/i&gt; [return]&lt;/dt&gt;   &lt;dd&gt;Only allow access to the module from the first time to the second each day. Both times should be specified in 24-hour HH:mm format.&lt;/dd&gt;   &lt;dt&gt;CMD &lt;b&gt;day&lt;/b&gt;=&lt;i&gt;day[,day,...]&lt;/i&gt; [return]&lt;/dt&gt;   &lt;dd&gt;Only allow access during certain days. Day is either a numerical value (Monday=1, Sunday=7) or a string (monday, tuesday etc)&lt;/dd&gt;&lt;/dl&gt;&lt;p&gt;    pattern is always a glob pattern (* = any characters, ? = any character).   &lt;/p&gt;&lt;p&gt;    return means that reaching this command results in immediate
Roxen.git/server/translations/eng/roxen_config.xml:2262:   a server configuration is created, this variable is set to the current   version. After that it's never changed automatically, thereby ensuring   that server configurations migrated from earlier Roxen versions is   kept at the right compatibility level.&lt;/p&gt;      &lt;p&gt;This variable may be changed manually, but it's advisable to test   the site carefully afterwards. A reload of the whole server   configuration is required to propagate the change properly to all   modules.&lt;/p&gt;    - &lt;p&gt;Available compatibility levels: - &lt;table&gt; - &lt;tr valign='top'&gt;&lt;td&gt;2.1&amp;nbsp;&amp;nbsp;&lt;/td&gt; -  &lt;td&gt;Corresponds to Roxen WebServer 2.1.&lt;/td&gt;&lt;/tr&gt; - &lt;tr valign='top'&gt;&lt;td&gt;2.2&amp;nbsp;&amp;nbsp;&lt;/td&gt; -  &lt;td&gt;Corresponds to Roxen WebServer 2.2.&lt;/td&gt;&lt;/tr&gt; - &lt;tr valign='top'&gt;&lt;td&gt;2.4&amp;nbsp;&amp;nbsp;&lt;/td&gt; -  &lt;td&gt;Corresponds to Roxen WebServer 2.4. This version is also -  commonly known as 3.2 - the version number that applies to the -  release of Roxen CMS which contains Roxen WebServer 2.4.&lt;/td&gt;&lt;/tr&gt; - &lt;tr valign='top'&gt;&lt;td&gt;2.5&amp;nbsp;&amp;nbsp;&lt;/td&gt; -  &lt;td&gt;Corresponds to no released version. This compatibility level is -  only used to turn on some optimizations that have compatibility + &lt;p&gt;Compatibility level notes:&lt;/p&gt; +  + &lt;ul&gt; +  &lt;li&gt;2.4 also applies to the version commonly known as 3.2. That was +  the release of Roxen CMS which contained Roxen WebServer 2.4.&lt;/li&gt; +  +  &lt;li&gt;2.5 corresponds to no released version. This compatibility level +  is only used to turn on some optimizations that have compatibility    issues with 2.4, notably the optimization of cache static tags in -  the &amp;lt;cache&amp;gt; tag.&lt;/td&gt;&lt;/tr&gt; - &lt;tr valign='top'&gt;&lt;td&gt;3.3&amp;nbsp;&amp;nbsp;&lt;/td&gt; -  &lt;td&gt;Corresponds to Roxen 3.3.&lt;/td&gt;&lt;/tr&gt; - &lt;tr valign='top'&gt;&lt;td&gt;3.4&amp;nbsp;&amp;nbsp;&lt;/td&gt; -  &lt;td&gt;Corresponds to Roxen 3.4.&lt;/td&gt;&lt;/tr&gt; - &lt;tr valign='top'&gt;&lt;td&gt;4.0&amp;nbsp;&amp;nbsp;&lt;/td&gt; -  &lt;td&gt;Corresponds to Roxen 4.0.&lt;/td&gt;&lt;/tr&gt; - &lt;tr valign='top'&gt;&lt;td&gt;4.5&amp;nbsp;&amp;nbsp;&lt;/td&gt; -  &lt;td&gt;Corresponds to Roxen 4.5.&lt;/td&gt;&lt;/tr&gt; - &lt;tr valign='top'&gt;&lt;td&gt;5.0&amp;nbsp;&amp;nbsp;&lt;/td&gt; -  &lt;td&gt;Corresponds to Roxen 5.0.&lt;/td&gt;&lt;/tr&gt; - &lt;/table&gt;&lt;/p&gt;</o> +  the &amp;lt;cache&amp;gt; tag.&lt;/li&gt; +  +  &lt;li&gt;There are no compatibility differences between 5.0 and 5.1, so +  those two compatibility levels can be used interchangeably.&lt;/li&gt; + &lt;/ul&gt;</o>   <t></t>   </str>      <str id="387">   <o>Auto Restart: Schedule</o>   <t></t>   </str>      <str id="388">   <o>Automatically restart the server according to this schedule.</o>
Roxen.git/server/translations/eng/roxen_config.xml:2497:   <o>Internal</o>   <t></t>   </str>      <str id="441">   <o>External</o>   <t></t>   </str>      <str id="442"> - <o>The name of the database. To make it easy on your users, use all lowercaps characters, and avoid 'odd' characters </o> + <o>The name of the database. To make it easy on your users, please use + all lowercase characters, and avoid 'odd' characters.</o>   <t></t>   </str>      <str id="443"> - <o>The database type. Internal means that it will be created in the Roxen MySQL database, and the permissions of the database will be automatically manged by Roxen. External means that the database resides in another database.</o> + <o>The database type. &lt;i&gt;Internal&lt;/i&gt; means that it is created in the + local Roxen MySQL server, or some other MySQL server specified in the + URL setting of the chosen group. The permissions of the database are + manged by Roxen. &lt;i&gt;External&lt;/i&gt; means that the database resides in + another server, which can be another MySQL instance or something else.</o>   <t></t>   </str>      <str id="444">   <o>URL</o>   <t></t>   </str>      <str id="446"> - <o>This URL is only used for &lt;/i&gt;External&lt;i&gt; databases, it is totally ignored for databases defined internally in Roxen</o> + <o>The URL to the database. It is only used for &lt;i&gt;external&lt;/i&gt; + databases.</o>   <t></t>   </str>      <str id="447"> - <o>This group is used to group the databses. For external databases, the group can also be used to select which MySQL server the database should be created in</o> + <o>The group to put the database in. For &lt;i&gt;internal&lt;/i&gt; databases, the + URL setting in the group also specifies which MySQL server the + database is created in.</o>   <t></t>   </str>      <str id="448">   <o>Comment</o>   <t></t>   </str>      <str id="449">   <o>automatic</o>   <t></t>   </str>      <str id="450">   <o>Create a new database group</o>   <t></t>   </str>      <str id="451"> - <o>The groups are used mainly to group the databases in the - Administration interface, but also to indicate the default MySQL server - external databases will be created in. + <o>&lt;p&gt;The groups are used mainly to group the databases in the + Administration interface, but also to indicate the default MySQL + server external databases will be created in.&lt;/p&gt;    - &lt;p&gt; If a group has a URL set, it will be used to select the database - server in which the database will be created. Please note that this - server must be a MySQL server, nothing else will work. - </o> + &lt;p&gt;If a group has a URL set, it will be used to select the database + server in which the database will be created. Please note that it + must be a MySQL server.&lt;/p&gt;</o>   <t></t>   </str>      <str id="452">   <o>ID</o>   <t></t>   </str>      <str id="453"> - <o>The identifier of the group. This is used internally in Roxen, and must be unique. If you leave it as automatic, a ID will be selected automatically.</o> + <o>The identifier of the group. This is used internally in Roxen, and must be unique. If you leave it as automatic, an identifier is selected automatically.</o>   <t></t>   </str>      <str id="454"> - <o>The name of the database group. This is what is shown in the configuration interface</o> + <o>The name of the database group. This is what is shown in the configuration interface.</o>   <t></t>   </str>      <str id="455"> - <o>This URL is only used when &lt;/i&gt;Internal&lt;i&gt; databases is created in this group, and it specified which MySQL server the datbase should be created in. As an example, if you want all databases created in the group to end up in the MySQL running on the host &lt;/i&gt;wyrm&lt;i&gt;, using the account with the username &lt;/i&gt;foo&lt;i&gt; and password &lt;/i&gt;bar&lt;i&gt;, set this URL to &lt;/i&gt;foo:bar@wyrm&lt;i&gt;</o> + <o>This URL is used for &lt;i&gt;internal&lt;/i&gt; databases created in this group, + and it specifies which MySQL server they should be created in. As an + example, if you want all databases created in the group to end up in + the MySQL running on the host &lt;i&gt;wyrm&lt;/i&gt;, using the account with + the username &lt;i&gt;foo&lt;/i&gt; and password &lt;i&gt;bar&lt;/i&gt;, set this URL to + &lt;i&gt;foo:bar@wyrm&lt;/i&gt;.</o>   <t></t>   </str>      <str id="456">   <o>Cannot connect to %s</o>   <t></t>   </str>      <str id="457">   <o>A database group named %s already exists</o>
Roxen.git/server/translations/eng/roxen_config.xml:3554:   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> +  + <str id="1047"> + <o>Module is disabled</o> + <t></t> + </str> +  + <str id="1048"> + <o>Server too busy message</o> + <t></t> + </str> +  + <str id="1049"> + <o>What to return if the server is too busy. See also "Handler queue timeout".</o> + <t></t> + </str> +  + <str id="1050"> + <o>Handler queue timeout</o> + <t></t> + </str> +  + <str id="1051"> + <o>Requests that have been waiting this many seconds on + the handler queue will not be processed. Instead, a 503 error code and the + "Server too busy message" will be returned to the client. This may help the + server to cut down the queue length after spikes of heavy load.</o> + <t></t> + </str> +  + <str id="1052"> + <o>Proxy: Use proxy (experimental)</o> + <t></t> + </str> +  + <str id="1053"> + <o>Use proxy for outgoing requests. E.g. when browsing external web sites through the Linkbrowser or when Insert cached-href fetches data from an external location.</o> + <t></t> + </str> +  + <str id="1054"> + <o>Proxy: Proxy URL</o> + <t></t> + </str> +  + <str id="1055"> + <o>The URL of the proxy to use for outgoing requests.</o> + <t></t> + </str> +  + <str id="1056"> + <o>Proxy: Proxy username</o> + <t></t> + </str> +  + <str id="1057"> + <o>Username for proxy authorization.</o> + <t></t> + </str> +  + <str id="1058"> + <o>Proxy: Proxy password</o> + <t></t> + </str> +  + <str id="1059"> + <o>Password for proxy authorization.</o> + <t></t> + </str> +  + <str id="1060"> + <o>System load</o> + <t></t> + </str> +  + <str id="1061"> + <o>The directory the backup will be saved in. If you chose auto, Roxen + will generate a directory name that includes the database name and + today's date in &lt;tt&gt;$VARDIR/backup&lt;/tt&gt; (%s).</o> + <t></t> + </str> +  + <str id="1062"> + <o>Error running query %d: %s</o> + <t></t> + </str> +  + <str id="1063"> + <o>Error connecting to database: </o> + <t></t> + </str> +  + <str id="1064"> + <o>Tip: Put '--' on a line to ignore everything below it.</o> + <t></t> + </str> +  + <str id="1065"> + <o>Uncheck/Check All</o> + <t></t> + </str> +  + <str id="1066"> + <o>SNMP status</o> + <t></t> + </str> +  + <str id="1067"> + <o>Global SNMP server statistics</o> + <t></t> + </str>