You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficserver.apache.org by ig...@apache.org on 2010/11/24 18:51:54 UTC
svn commit: r1038726 -
/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/files.en.mdtext
Author: igalic
Date: Wed Nov 24 17:51:54 2010
New Revision: 1038726
URL: http://svn.apache.org/viewvc?rev=1038726&view=rev
Log:
perl -p -i -e 's/\blog2\b/log/g' *.htm *.html for TS-555 (last commit message was wrong)
Modified:
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/files.en.mdtext
Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/files.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/files.en.mdtext?rev=1038726&r1=1038725&r2=1038726&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/files.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/files.en.mdtext Wed Nov 24 17:51:54 2010
@@ -912,7 +912,7 @@ The following list shows the `LogObject`
`<RollingEnabled = "truth value"/>`
: Enables or disables log file rolling for the `LogObject`. This
setting overrides the value for the
- *`proxy.config.log2.rolling_enabled`* variable in the
+ *`proxy.config.log.rolling_enabled`* variable in the
`records.config` file. Set *`truth value`* to one of the
following values:
@@ -934,7 +934,7 @@ The following list shows the `LogObject`
you to specify different rolling intervals for different
`LogObjects`.
This setting overrides the value for
- *`proxy.config.log2.rolling_interval_sec`* in the
+ *`proxy.config.log.rolling_interval_sec`* in the
`records.config` file.
`<RollingOffsetHr = "hour"/>`
@@ -943,7 +943,7 @@ The following list shows the `LogObject`
produced only at that time. The impact of this setting is only
noticeable if the rolling interval is larger than one hour.
This setting overrides the configuration setting
- for *`proxy.config.log2.rolling_offset_hr`* in the
+ for *`proxy.config.log.rolling_offset_hr`* in the
`records.config` file.
`<RollingSizeMb = "size_in_MB"/>`
@@ -2322,7 +2322,7 @@ the `records.config` file.
**Logging Config**
-*`proxy.config.log2.logging_enabled`*
+*`proxy.config.log.logging_enabled`*
: `INT`
: `3`
: Enables and disables event logging:
@@ -2334,44 +2334,44 @@ the `records.config` file.
Refer to [Working with Log Files](log).
-*`proxy.config.log2.max_secs_per_buffer`*
+*`proxy.config.log.max_secs_per_buffer`*
: `INT`
: `5`
: The maximum amount of time before data in the buffer is flushed to
disk.
-*`proxy.config.log2.max_space_mb_for_logs`*
+*`proxy.config.log.max_space_mb_for_logs`*
: `INT`
: `2000`
: The amount of space allocated to the logging directory (in MB).
-*`proxy.config.log2.max_space_mb_for_orphan_logs`*
+*`proxy.config.log.max_space_mb_for_orphan_logs`*
: `INT`
: `25`
: The amount of space allocated to the logging directory (in MB) if
this node is acting as a collation client.
-*`proxy.config.log2.max_space_mb_headroom`*
+*`proxy.config.log.max_space_mb_headroom`*
: `INT`
: `10`
: The tolerance for the log space limit (in bytes).
- If the variable *`proxy.config.log2.auto_delete_rolled_file`*
+ If the variable *`proxy.config.log.auto_delete_rolled_file`*
is set to `1` (enabled), then autodeletion of log files is
triggered when the amount of free space available in the logging
directory is less than the value specified here.
-*`proxy.config.log2.hostname`*
+*`proxy.config.log.hostname`*
: `STRING`
: `localhost`
: The hostname of the machine running Traffic Server.
-*`proxy.config.log2.logfile_dir`*
+*`proxy.config.log.logfile_dir`*
: `STRING`
: `install_dir /logs`
: The full path to the logging directory.
-*`proxy.config.log2.logfile_perm`*
+*`proxy.config.log.logfile_perm`*
: `STRING`
: `rw-r--r--`
: The log file permissions. The standard UNIX file permissions are
@@ -2388,12 +2388,12 @@ the `records.config` file.
configuration file. Permissions for existing log files are not
changed when the configuration is changed.
-*`proxy.config.log2.custom_logs_enabled`*
+*`proxy.config.log.custom_logs_enabled`*
: `INT`
: `0`
: Enables (`1`) or disables (`0`) custom logging.
-*`proxy.config.log2.xml_logs_config`*
+*`proxy.config.log.xml_logs_config`*
: `INT`
: `1`
: Enables (`1`) or disables (`0`) extended custom logging using an
@@ -2405,12 +2405,12 @@ the `records.config` file.
logging, you should use the more versatile XML-based custom
formats.
-*`proxy.config.log2.squid_log_enabled`*
+*`proxy.config.log.squid_log_enabled`*
: `INT`
: `1`
: Enables (`1`) or disables (`0`) the squid log file format.
-*`proxy.config.log2.squid_log_is_ascii`*
+*`proxy.config.log.squid_log_is_ascii`*
: `INT`
: `1`
: The squid log file type:
@@ -2418,23 +2418,23 @@ the `records.config` file.
`1` = ASCII
`0` = binary
-*`proxy.config.log2.squid_log_name`*
+*`proxy.config.log.squid_log_name`*
: `STRING`
: `squid`
: The squid log filename.
-*`proxy.config.log2.squid_log_header`*
+*`proxy.config.log.squid_log_header`*
: `STRING`
: `NULL`
: The squid log file header text.
-*`proxy.config.log2.common_log_enabled`*
+*`proxy.config.log.common_log_enabled`*
: `INT`
: `0`
: Enables (`1`) or disables (`0`) the Netscape common log file
format.
-*`proxy.config.log2.common_log_is_ascii`*
+*`proxy.config.log.common_log_is_ascii`*
: `INT`
: `1`
: The Netscape common log file type:
@@ -2442,23 +2442,23 @@ the `records.config` file.
`1` = ASCII
`0` = binary
-*`proxy.config.log2.common_log_name`*
+*`proxy.config.log.common_log_name`*
: `STRING`
: `common`
: The Netscape common log filename.
-*`proxy.config.log2.common_log_header`*
+*`proxy.config.log.common_log_header`*
: `STRING`
: `NULL`
: The Netscape common log file header text.
-*`proxy.config.log2.extended_log_enabled`*
+*`proxy.config.log.extended_log_enabled`*
: `INT`
: `0`
: Enables (`1`) or disables (`0`) the Netscape extended log file
format.
-*`proxy.confg.log2.extended_log_is_ascii`*
+*`proxy.confg.log.extended_log_is_ascii`*
: `INT`
: `1`
: The Netscape extended log file type:
@@ -2466,23 +2466,23 @@ the `records.config` file.
`1` = ASCII
`0` = binary
-*`proxy.config.log2.extended_log_name`*
+*`proxy.config.log.extended_log_name`*
: `STRING`
: `extended`
: The Netscape extended log filename.
-*`proxy.config.log2.extended_log_header`*
+*`proxy.config.log.extended_log_header`*
: `STRING`
: `NULL`
: The Netscape extended log file header text.
-*`proxy.config.log2.extended2_log_enabled`*
+*`proxy.config.log.extended2_log_enabled`*
: `INT`
: `0`
: Enables (`1`) or disables (`0`) the Netscape Extended-2 log file
format.
-*`proxy.config.log2.extended2_log_is_ascii`*
+*`proxy.config.log.extended2_log_is_ascii`*
: `INT`
: `1`
: The Netscape Extended-2 log file type:
@@ -2490,23 +2490,23 @@ the `records.config` file.
`1` = ASCII
`0` = binary
-*`proxy.config.log2.extended2_log_name`*
+*`proxy.config.log.extended2_log_name`*
: `STRING`
: `extended2`
: The Netscape Extended-2 log filename.
-*`proxy.config.log2.extended2_log_header`*
+*`proxy.config.log.extended2_log_header`*
: `STRING`
: `NULL`
: The Netscape Extended-2 log file header text.
-*`proxy.config.log2.separate_icp_logs`*
+*`proxy.config.log.separate_icp_logs`*
: `INT`
: `0`
: When enabled (`1`), configures Traffic Server to store ICP
transactions in a separate log file.
-*`proxy.config.log2.separate_host_logs`*
+*`proxy.config.log.separate_host_logs`*
: `INT`
: `0`
: When enabled (`1`), configures Traffic Server to create a separate
@@ -2515,7 +2515,7 @@ the `records.config` file.
Refer to [HTTP Host Log Splitting](log#HTTPHostLogSplitting).
-*`proxy.local.log2.collation_mode`*
+*`proxy.local.log.collation_mode`*
: `INT`
: `0`
: The log collation mode:
@@ -2538,36 +2538,36 @@ the `records.config` file.
logging, you should use the more versatile XML-based custom
formats.
-*`proxy.confg.log2.collation_host`*
+*`proxy.confg.log.collation_host`*
: `STRING`
: `NULL`
: The hostname of the log collation server.
-*`proxy.config.log2.collation_port`*
+*`proxy.config.log.collation_port`*
: `INT`
: `8085`
: The port used for communication between the collation server and
client.
-*`proxy.config.log2.collation_secret`*
+*`proxy.config.log.collation_secret`*
: `STRING`
: `foobar`
: The password used to validate logging data and prevent the exchange
of unauthorized information when a collation server is being used.
-*`proxy.config.log2.collation_host_tagged`*
+*`proxy.config.log.collation_host_tagged`*
: `INT`
: `0`
: When enabled (`1`), configures Traffic Server to include the
hostname of the collation client that generated the log entry in
each entry.
-*`proxy.config.log2.collation_retry_sec`*
+*`proxy.config.log.collation_retry_sec`*
: `INT`
: `5`
: The number of seconds between collation server connection retries.
-*`proxy.config.log2.rolling_enabled`*
+*`proxy.config.log.rolling_enabled`*
: `INT`
: `1`
: Specifies how log files are rolled. You can specify the following
@@ -2576,11 +2576,11 @@ the `records.config` file.
`0` = disables log file rolling
`1` = enables log file rolling at specific intervals during the day
- (specified with the *`proxy.config.log2.rolling_interval_sec`*
- and *`proxy.config.log2.rolling_offset_hr`* variables)
+ (specified with the *`proxy.config.log.rolling_interval_sec`*
+ and *`proxy.config.log.rolling_offset_hr`* variables)
`2` = enables log file rolling when log files reach a specific size
- (specified with the *`proxy.config.log2.rolling_size_mb`*
+ (specified with the *`proxy.config.log.rolling_size_mb`*
variable)
`3` = enables log file rolling at specific intervals during the day
@@ -2590,30 +2590,30 @@ the `records.config` file.
when log files reach a specific size (i.e., at a specified time if
the file is of the specified size)
-*`proxy.config.log2.rolling_interval_sec`*
+*`proxy.config.log.rolling_interval_sec`*
: `INT`
: `86400`
: The log file rolling interval, in seconds. The minimum value is
`300` (5 minutes). The maximum value is 86400 seconds (one day).
-*`proxy.config.log2.rolling_offset_hr`*
+*`proxy.config.log.rolling_offset_hr`*
: `INT`
: `0`
: The file rolling offset hour. The hour of the day that starts the
log rolling period.
-*`proxy.config.log2.rolling_size_mb`*
+*`proxy.config.log.rolling_size_mb`*
: `INT`
: `10`
: The size that log files must reach before rolling takes place.
-*`proxy.config.log2.auto_delete_rolled_files`*
+*`proxy.config.log.auto_delete_rolled_files`*
: `INT`
: `1`
: Enables (`1`) or disables (`0`) automatic deletion of rolled
files.
-*`proxy.config.log2.sampling_frequency`*
+*`proxy.config.log.sampling_frequency`*
: `INT`
: `1`
: Configures Traffic Server to log only a sample of transactions