Branch: Tag:

2008-01-10

2008-01-10 15:36:38 by 0

Updates.

Rev: server/base_server/configuration.pike:1.645
Rev: server/base_server/global_variables.pike:1.105
Rev: server/base_server/roxen.pike:1.972
Rev: server/config_interface/dbs/browser.pike:1.62
Rev: server/config_interface/dbs/db_matrix.pike:1.28
Rev: server/config_interface/dbs/index.html:1.13
Rev: server/config_interface/dbs/subtabs.pike:1.17
Rev: server/modules/configuration/config_tags.pike:1.196
Rev: server/translations/ces/admin_tasks.xml:1.28
Rev: server/translations/ces/roxen_config.xml:1.51
Rev: server/translations/deu/admin_tasks.xml:1.28
Rev: server/translations/deu/roxen_config.xml:1.61
Rev: server/translations/deu/roxen_message.xml:1.16
Rev: server/translations/eng/admin_tasks.xml:1.29
Rev: server/translations/eng/roxen_config.xml:1.57
Rev: server/translations/eng/roxen_message.xml:1.26
Rev: server/translations/hun/admin_tasks.xml:1.22
Rev: server/translations/hun/roxen_config.xml:1.47
Rev: server/translations/jpn/admin_tasks.xml:1.22
Rev: server/translations/jpn/roxen_config.xml:1.47
Rev: server/translations/nld/admin_tasks.xml:1.28
Rev: server/translations/nld/roxen_config.xml:1.51
Rev: server/translations/swe/admin_tasks.xml:1.25
Rev: server/translations/swe/roxen_config.xml:1.66
Rev: server/translations/swe/roxen_message.xml:1.27

156:   </str>      <str id="27"> - <o>What format to use for logging. The syntax is: - &lt;pre&gt;response-code or *: Log format for that response code + <o>Describes the format to use for access logging. The log file can also + receive messages for various internal activities.    - Log format is normal characters, or one or more of the variables below: + Empty lines and lines beginning with '&lt;code&gt;#&lt;/code&gt;' are ignored. + Other lines describes how to log either an access or an internal + event.    - \n \t \r -- As in C, newline, tab and linefeed - $char(int) -- Insert the (1 byte) character specified by the integer. - $wchar(int) -- Insert the (2 byte) word specified by the integer. - $int(int) -- Insert the (4 byte) word specified by the integer. - $^ -- Supress newline at the end of the logentry - $host -- The remote host name, or ip number. - $vhost -- The Host request-header sent by the client, or - if none - $ip_number -- The remote ip number. - $bin-ip_number -- The remote host id as a binary integer number. - $cern_date -- Cern Common Log file format date. - $bin-date -- Time, but as an 32 bit integer in network byteorder - $method -- Request method - $resource -- Resource identifier - $full_resource -- Full requested resource, including any query fields - $protocol -- The protocol used (normally HTTP/1.0) - $response -- The response code sent - $bin-response -- The response code sent as a binary short number - $length -- The length of the data section of the reply - $bin-length -- Same, but as an 32 bit integer in network byteorder - $request-time -- The time the request took (seconds) - $referer -- The header 'referer' from the request, or '-'. - $user_agent -- The header 'User-Agent' from the request, or '-'. - $user_agent_raw -- Same, but spaces in the name are not encoded to %20. - $user -- the name of the auth user used, if any - $user_id -- A unique user ID, if cookies are supported, -  by the client, otherwise '0' - $cache-status -- A comma separated list of words (containing no -  whitespace) that describes which cache(s) the page -  was delivered from: -  protcache -- The low-level cache in the HTTP -  protocol module. -  xsltcache -- The XSLT cache. -  pcoderam -- RXML parse tree RAM cache. -  pcodedisk -- RXML parse tree persistent cache. -  cachetag -- No RXML &amp;lt;cache&amp;gt; tag misses. -  nocache -- No hit in any known cache. - &lt;/pre&gt;</o> + &lt;p&gt;A line to format an access logging message is one of:&lt;/p&gt; +  + &lt;pre&gt;&lt;i&gt;&amp;lt;response code&amp;gt;&lt;/i&gt;: &lt;i&gt;&amp;lt;log format&amp;gt;&lt;/i&gt; + *: &lt;i&gt;&amp;lt;log format&amp;gt;&lt;/i&gt; + &lt;/pre&gt; +  + &lt;p&gt;&lt;i&gt;&amp;lt;response code&amp;gt;&lt;/i&gt; is an HTTP status code. The + corresponding &lt;i&gt;&amp;lt;log format&amp;gt;&lt;/i&gt; is used for all responses + matching that code. It's described in more detail below. If + '&lt;code&gt;*&lt;/code&gt;' is used instead of a response code then that line + matches all responses that aren't matched by any specific response + code line.&lt;/p&gt; +  + &lt;p&gt;A line to format an event logging message is one of:&lt;/p&gt; +  + &lt;pre&gt;&lt;i&gt;&amp;lt;facility&amp;gt;&lt;/i&gt;/&lt;i&gt;&amp;lt;action&amp;gt;&lt;/i&gt;: &lt;i&gt;&amp;lt;log format&amp;gt;&lt;/i&gt; + &lt;i&gt;&amp;lt;facility&amp;gt;&lt;/i&gt;/*: &lt;i&gt;&amp;lt;log format&amp;gt;&lt;/i&gt; + */*: &lt;i&gt;&amp;lt;log format&amp;gt;&lt;/i&gt; + &lt;/pre&gt; +  + &lt;p&gt;&lt;i&gt;&amp;lt;facility&amp;gt;&lt;/i&gt; matches an identifier for the Roxen module + or subsystem that the event comes from. Facility identifiers always + starts with a character in &lt;code&gt;[a-zA-Z0-9]&lt;/code&gt; and contains only + characters in &lt;code&gt;[-_.#a-zA-Z0-9]&lt;/code&gt;. If '&lt;code&gt;*&lt;/code&gt;' is + used instead of &lt;i&gt;&amp;lt;facility&amp;gt;&lt;/i&gt; then that line matches all + facilities that aren't matched by any other line.&lt;/p&gt; +  + &lt;p&gt;&lt;i&gt;&amp;lt;action&amp;gt;&lt;/i&gt; matches an identifier for a specific kind of + event logged by a facility. An action identifier contains only + characters in &lt;code&gt;[-_.#a-zA-Z0-9]&lt;/code&gt;. '&lt;code&gt;*&lt;/code&gt;' may be + used instead of an &lt;i&gt;&amp;lt;action&amp;gt;&lt;/i&gt; to match all events logged by + a facility that aren't matched by any other line.&lt;/p&gt; +  + &lt;p&gt;&lt;i&gt;&amp;lt;log format&amp;gt;&lt;/i&gt; 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 '&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;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; + &lt;tr&gt;&lt;td&gt;$int(int)&lt;/td&gt; +  &lt;td&gt;Insert the specified integer using 4 bytes in network byte +  order. Specify a negative integer to get the opposite (i.e. big +  endian) order.&lt;/td&gt;&lt;/tr&gt; + &lt;tr&gt;&lt;td&gt;$^&lt;/td&gt; +  &lt;td&gt;Suppress newline at the end of the logentry.&lt;/td&gt;&lt;/tr&gt; + &lt;tr&gt;&lt;td&gt;$date&lt;/td&gt; +  &lt;td&gt;Local date formatted like '&lt;code&gt;2001-01-17&lt;/code&gt;'.&lt;/td&gt;&lt;/tr&gt; + &lt;tr&gt;&lt;td&gt;$time&lt;/td&gt; +  &lt;td&gt;Local time formatted like '&lt;code&gt;13:00:00&lt;/code&gt;'.&lt;/td&gt;&lt;/tr&gt; + &lt;tr&gt;&lt;td&gt;$cern-date&lt;/td&gt; +  &lt;td&gt;Local date and time in CERN Common Log file format, i.e. +  like '&lt;code&gt;17/Jan/2001:13:00:00 +0200&lt;/code&gt;'.&lt;/td&gt;&lt;/tr&gt; + &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 indentifier (otherwise).&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;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 +  '-' if none is provided. If multiple headers or multiple values are +  given the first value is logged; this should correspond to the +  originating computer.&lt;/td&gt;&lt;/tr&gt; + &lt;tr&gt;&lt;td&gt;$method&lt;/td&gt; +  &lt;td&gt;Request method.&lt;/td&gt;&lt;/tr&gt; + &lt;tr&gt;&lt;td&gt;$full-resource&lt;/td&gt; +  &lt;td&gt;Full requested resource, including any query fields.&lt;/td&gt;&lt;/tr&gt; + &lt;tr&gt;&lt;td&gt;$protocol&lt;/td&gt; +  &lt;td&gt;The protocol used (normally HTTP/1.1).&lt;/td&gt;&lt;/tr&gt; + &lt;tr&gt;&lt;td&gt;$response&lt;/td&gt; +  &lt;td&gt;The response code sent.&lt;/td&gt;&lt;/tr&gt; + &lt;tr&gt;&lt;td&gt;$bin-response&lt;/td&gt; +  &lt;td&gt;The response code sent as a binary short number.&lt;/td&gt;&lt;/tr&gt; + &lt;tr&gt;&lt;td&gt;$length&lt;/td&gt; +  &lt;td&gt;The length of the data section of the reply.&lt;/td&gt;&lt;/tr&gt; + &lt;tr&gt;&lt;td&gt;$bin-length&lt;/td&gt; +  &lt;td&gt;Same, but as a 32 bit integer in network byte order.&lt;/td&gt;&lt;/tr&gt; + &lt;tr&gt;&lt;td&gt;$request-time&lt;/td&gt; +  &lt;td&gt;The time the request took (seconds). Note that this measures +  real time, not virtual process time. I.e. if there are other +  processes using the CPU then this will not accurately show the +  time that the Roxen server process spent.&lt;/td&gt;&lt;/tr&gt; + &lt;tr&gt;&lt;td&gt;$etag&lt;/td&gt; +  &lt;td&gt;The entity tag (aka ETag) header of the result.&lt;/td&gt;&lt;/tr&gt; + &lt;tr&gt;&lt;td&gt;$referer&lt;/td&gt; +  &lt;td&gt;The header 'referer' from the request, or '-'.&lt;/td&gt;&lt;/tr&gt; + &lt;tr&gt;&lt;td&gt;$user-agent&lt;/td&gt; +  &lt;td&gt;The header 'User-Agent' from the request, or '-'.&lt;/td&gt;&lt;/tr&gt; + &lt;tr&gt;&lt;td&gt;$user-agent-raw&lt;/td&gt; +  &lt;td&gt;Same, but spaces in the name are not encoded to %20.&lt;/td&gt;&lt;/tr&gt; + &lt;tr&gt;&lt;td&gt;$user&lt;/td&gt; +  &lt;td&gt;The name of the user, if any is given using the HTTP basic +  authentication method.&lt;/td&gt;&lt;/tr&gt; + &lt;tr&gt;&lt;td&gt;$user-id&lt;/td&gt; +  &lt;td&gt;A unique user ID, if cookies are supported, by the client, +  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 which cache(s) the page was delivered from: +  +  &lt;table&gt;&lt;tbody valign='top'&gt; +  &lt;tr&gt;&lt;td&gt;protcache&lt;/td&gt; +  &lt;td&gt;The low-level cache in the HTTP protocol module.&lt;/td&gt;&lt;/tr&gt; +  &lt;tr&gt;&lt;td&gt;protstore&lt;/td&gt; +  &lt;td&gt;The page got stored in the low-level cache in the HTTP +  protocol module.&lt;/td&gt;&lt;/tr&gt; +  &lt;tr&gt;&lt;td&gt;xsltcache&lt;/td&gt; +  &lt;td&gt;The XSLT cache.&lt;/td&gt;&lt;/tr&gt; +  &lt;tr&gt;&lt;td&gt;pcoderam&lt;/td&gt; +  &lt;td&gt;RXML parse tree RAM cache.&lt;/td&gt;&lt;/tr&gt; +  &lt;tr&gt;&lt;td&gt;pcodedisk&lt;/td&gt; +  &lt;td&gt;RXML parse tree persistent cache.&lt;/td&gt;&lt;/tr&gt; +  &lt;tr&gt;&lt;td&gt;cachetag&lt;/td&gt; +  &lt;td&gt;No RXML &amp;lt;cache&amp;gt; tag misses.&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;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: sbfs&lt;/dt&gt; +  &lt;dd&gt;&lt;p&gt;A SiteBuilder file system.&lt;/p&gt; +  +  &lt;p&gt;The actions &lt;code&gt;commit&lt;/code&gt;, &lt;code&gt;purge&lt;/code&gt;, +  &lt;code&gt;mkdir&lt;/code&gt;, &lt;code&gt;set-dir-md&lt;/code&gt;, and +  &lt;code&gt;rmdir&lt;/code&gt; are logged for file system changes except those +  in edit areas.&lt;/p&gt; +  +  &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;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; +  &lt;tr&gt;&lt;td&gt;$revision&lt;/td&gt; +  &lt;td&gt;The committed revision number, a dotted decimal.&lt;/td&gt;&lt;/tr&gt; +  &lt;tr&gt;&lt;td&gt;$comment&lt;/td&gt; +  &lt;td&gt;The commit message.&lt;/td&gt;&lt;/tr&gt; +  &lt;tr&gt;&lt;td&gt;$request-time&lt;/td&gt; +  &lt;td&gt;This is set for the action &lt;code&gt;crawl-file&lt;/code&gt;. It's +  similar to &lt;code&gt;$request-time&lt;/code&gt; for normal requests, +  except that it measures the whole time it took for the +  persistent cache crawler to process the page. That includes +  all crawled variants and the saving of the entry to the +  database.&lt;/td&gt;&lt;/tr&gt; +  &lt;/tbody&gt;&lt;/table&gt;&lt;/dd&gt; + &lt;/dl&gt;</o>   <t></t>   </str>   
825:   </str>      <str id="159"> - <o>Locale, used to localize all messages in Roxen. Standard means using the default locale, which varies according to the value of the 'LANG' environment variable.</o> + <o>Locale, used to localize all messages in Roxen. Standard means using the default locale, which varies according to the values of the 'LC_MESSAGES' and 'LANG' environment variables.</o>   <t></t>   </str>   
1837:   <t></t>   </str>    - <str id="375"> - <o>KiB</o> - <t></t> - </str> +     -  +    <str id="376">   <o>Name</o>   <t></t>
1853:   </str>      <str id="378"> - <o>Clear query</o> + <o>Reset query</o>   <t></t>   </str>   
1867:   <t></t>   </str>    - <str id="381"> - <o>Failed to connect</o> - <t></t> - </str> +     -  +    <str id="382">   <o>Failed to enable %s</o>   <t></t>
2209:   <t></t>   </str>    - <str id="427"> - <o>the deleted module %s from %s</o> - <t></t> - </str> +     -  +    <str id="428"> - <o>Defined by %s</o> + <o>Defined by %s.</o>   <t></t>   </str>      <str id="429"> - <o>The table is known as '%s' in the module</o> + <o>The table is known as %O in the module.</o>   <t></t>   </str>      <str id="430"> - <o>The table is an anymous table defined by the module</o> + <o>The table is an anonymous table defined by the module.</o>   <t></t>   </str>   
2254:   <t></t>   </str>    - <str id="436"> - <o>The -  &lt;i&gt;local&lt;/i&gt; database contains data that should not -  be shared. The &lt;i&gt;docs&lt;/i&gt; database contains all -  documentation. -  </o> - <t></t> - </str> +     -  +    <str id="437">   <o>Create new database</o>   <t></t>
2647:   </str>      <str id="337"> - <o>If enabled, Roxen will enable various replication systems needed to set up multiple frontend systems. You will need a database named 'replicate' that recides in a shared mysql server for this to work. Also, all servers has to have this flag set. Roxen must be restarted before changes to this variable takes effect.</o> + <o>If enabled, Roxen will enable various replication systems needed to set up multiple frontend systems. You will need a database named 'replicate' that resides in a shared mysql server for this to work. Also, all servers has to have this flag set. Roxen must be restarted before changes to this variable takes effect.</o>   <t></t>   </str>   
2657:   </str>      <str id="362"> - <o>Are you sure you want to delete the database %s? No data will be deleted from the remote datbase.</o> + <o>Are you sure you want to delete the database %s? No data will be deleted from the remote database.</o>   <t></t>   </str>   
2697:   </str>      <str id="506"> - <o>Member of the %s database group</o> + <o>Member of the %s database group.</o>   <t></t>   </str>   
2911:   <o>Really Compact</o>   <t></t>   </str> +  + <str id="258"> + <o>Logging: Compress log file</o> + <t></t> + </str> +  + <str id="259"> + <o>Path to a program to compress log files, e.g. &lt;tt&gt;/usr/bin/bzip2&lt;/tt&gt; or &lt;tt&gt;/usr/bin/gzip&lt;/tt&gt;. &lt;b&gt;Note&amp;nbsp;1:&lt;/b&gt; The active log file is never compressed. Log rotation needs to be used using the "Log file" filename substitutions (e.g. &lt;tt&gt;$LOGDIR/mysite/Log.%y-%m-%d&lt;/tt&gt;). &lt;b&gt;Note&amp;nbsp;2:&lt;/b&gt; Compression is limited to scanning files with filename substitutions within a fixed directory (e.g. &lt;tt&gt;$LOGDIR/mysite/Log.%y-%m-%d&lt;/tt&gt;, not &lt;tt&gt;$LOGDIR/mysite/%y/Log.%m-%d&lt;/tt&gt;).</o> + <t></t> + </str> +  + <str id="532"> + <o>Show this string in header</o> + <t></t> + </str> +  + <str id="533"> + <o>Enter a identifier that will be displayed in the head of config interface. This makes it easier to distinguish between different site configurations. </o> + <t></t> + </str> +  + <str id="534"> + <o>Logging: Dump threads by file polling</o> + <t></t> + </str> +  + <str id="535"> + <o>&lt;p&gt;This option can be used to produce dumps of all the threads in the + debug log in situations where the Administration Interface doesn't + respond.&lt;/p&gt; +  + &lt;p&gt;It works by checking for a file called "&lt;i&gt;&amp;lt;config + name&amp;gt;&lt;/i&gt;.dump_threads" in the same directory as the debug log. + &lt;i&gt;&amp;lt;config name&amp;gt;&lt;/i&gt; is the name of the server configuration, + i.e. the same as the base name of the debug log files (typically + "default"). If this file exists, a thread dump is generated and the + file is deleted. If a file on the form "&lt;i&gt;&amp;lt;config + name&amp;gt;&lt;/i&gt;.dump_threads.&lt;i&gt;&amp;lt;n&amp;gt;&lt;/i&gt;", where &lt;i&gt;&amp;lt;n&amp;gt;&lt;/i&gt; + is an integer, exists then &lt;i&gt;n&lt;/i&gt; thread dumps are generated in one + minute intervals.&lt;/p&gt; +  + &lt;p&gt;Note that this method normally isn't necessary in unix-like + environments; there you can just send a SIGQUIT signal to the pike + process to get a thread dump.&lt;/p&gt; +  + &lt;p&gt;Enabling this creates a dedicated thread.&lt;/p&gt;</o> + <t></t> + </str> +  + <str id="536"> + <o>Change default character set</o> + <t></t> + </str> +  + <str id="537"> + <o>Repair all tables</o> + <t></t> + </str> +  + <str id="538"> + <o>Optimize all tables</o> + <t></t> + </str> +  + <str id="539"> + <o>Changing default character set for %s</o> + <t></t> + </str> +  + <str id="540"> + <o>Old default character set</o> + <t></t> + </str> +  + <str id="541"> + <o>New default character set</o> + <t></t> + </str> +  + <str id="542"> + <o>the deleted site %O</o> + <t></t> + </str> +  + <str id="543"> + <o>%s in %s</o> + <t></t> + </str> +  + <str id="544"> + <o>the deleted module %s in %s</o> + <t></t> + </str> +  + <str id="545"> + <o>the deleted module %s</o> + <t></t> + </str> +  + <str id="546"> + <o>Internal data that cannot be shared between servers.</o> + <t></t> + </str> +  + <str id="547"> + <o>Internal data that may be shared between servers.</o> + <t></t> + </str> +  + <str id="548"> + <o>Default charset:</o> + <t></t> + </str> +  + <str id="549"> + <o>No defined databases. + </o> + <t></t> + </str> +  + <str id="550"> + <o>Site Permissions</o> + <t></t> + </str> +  + <str id="551"> + <o>Module Priorities</o> + <t></t> + </str>