Author: igalic
Date: Mon May 16 23:01:38 2011
New Revision: 1103947

URL: http://svn.apache.org/viewvc?rev=1103947&view=rev
Log:
Fix up markup and content of some chapters, move out duplicate information on
directives into configuration-files.

Modified:
    
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/records.config.en.mdtext
    
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/event-logging-formats/index.en.mdtext
    
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/security-options/index.en.mdtext
    
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/traffic-line-commands/index.en.mdtext
    
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/traffic-server-error-messages/index.en.mdtext
    
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/working-log-files/index.en.mdtext

Modified: 
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/records.config.en.mdtext
URL: 
http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/records.config.en.mdtext?rev=1103947&r1=1103946&r2=1103947&view=diff
==============================================================================
--- 
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/records.config.en.mdtext
 (original)
+++ 
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/records.config.en.mdtext
 Mon May 16 23:01:38 2011
@@ -1206,6 +1206,9 @@ the `records.config` file.
 :   `INT`
 :   Default: `2000`
 :   The amount of space allocated to the logging directory (in MB).
+    
+    **Note:** All files in the logging directory contribute
+    to the space used, even if they are not log files.
 
 *`proxy.config.log.max_space_mb_for_orphan_logs`* 
{#proxy.config.log.max_space_mb_for_orphan_logs}
 :   `INT`
@@ -1230,9 +1233,14 @@ the `records.config` file.
 
 *`proxy.config.log.logfile_dir`* {#proxy.config.log.logfile_dir}
 :   `STRING`
-:   Default: `*install_dir*``/logs`
+:   Default: *`install_dir`*`/logs`
 :   The full path to the logging directory.
 
+    This can be an absolute path or a path relative to the directory in which 
Traffic Server is installed.
+
+    **Note:** The directory you specify must already exist.
+
+
 *`proxy.config.log.logfile_perm`* {#proxy.config.log.logfile_perm}
 :   `STRING`
 :   Default: `rw-r--r--`
@@ -1357,6 +1365,11 @@ the `records.config` file.
 :   When enabled (`1`), configures Traffic Server to store ICP
     transactions in a separate log file.
 
+    * `0` = separation is disabled, all ICP transactions are recorded in the 
same file as HTTP transactions
+    * `1` = all ICP transactions are recorded in a separate log file.
+    * `-1` = filter all ICP transactions from the default log files; ICP 
transactions are not logged anywhere.
+
+
 *`proxy.config.log.separate_host_logs`* {#proxy.config.log.separate_host_logs}
 :   `INT`
 :   Default: `0`
@@ -1443,6 +1456,9 @@ the `records.config` file.
 :   The log file rolling interval, in seconds. The minimum value is
     `300` (5 minutes). The maximum value is 86400 seconds (one day).
 
+    **Note:** If you start Traffic Server within a few minutes of the next 
rolling time, 
+    then rolling might not occur until the next rolling time.
+
 *`proxy.config.log.rolling_offset_hr`* {#proxy.config.log.rolling_offset_hr}
 :   `INT`
 :   Default: `0`

Modified: 
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/event-logging-formats/index.en.mdtext
URL: 
http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/event-logging-formats/index.en.mdtext?rev=1103947&r1=1103946&r2=1103947&view=diff
==============================================================================
--- 
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/event-logging-formats/index.en.mdtext
 (original)
+++ 
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/event-logging-formats/index.en.mdtext
 Mon May 16 23:01:38 2011
@@ -94,26 +94,22 @@ Notice:    Licensed to the Apache Softwa
     hh:mm:ss, where hh is the two-digit hour in 24-hour format, mm is the 
two-digit 
     minutes value, and ss is the 2-digit seconds value (for example, 
16:01:19). 
 
-`cqtx`
+`cqtx` {#cqtx}
 :   The full HTTP client request text, minus headers; for example, 
  
          GET http://www.company.com HTTP/1.0
 
     In reverse proxy mode, Traffic Server logs the rewritten/mapped URL 
(according 
-    to the rules in the ` remap.config` file), and _ not_ the 
pristine/unmapped 
-    URL. To configure Traffic Server to log the original, unmapped URL, set 
the 
-    variable ` _proxy.config.url_remap.pristine_host_hdr _` in the ` 
records.config` 
-    file to ` 1` .
+    to the rules in the [`remap.config`](../configuration-files/remap.config) 
file), and _not _ the pristine/unmapped 
+    URL. To configure Traffic Server to log the original, unmapped URL, set 
the variable
+    
[_`proxy.config.url_remap.pristine_host_hdr`_](../configuration-files/records.config#proxy.config.url_remap.pristine_host_hdr)
+    in the [`records.config`](../configuration-files/records.config) file to 
`1` .
 
 `cqu`
 :   The universal resource identifier (URI) of the request from client to 
Traffic 
     Server (subset of ` cqtx` ).
 
-    In reverse proxy mode, Traffic Server logs the rewritten/mapped URL 
(according 
-    to the rules in the ` remap.config` file), and _ not _ the 
pristine/unmapped 
-    URL. To configure Traffic Server to log the original, unmapped URL, set 
the 
-    variable ` _proxy.config.url_remap.pristine_host_hdr _` in the ` 
records.config` 
-    file to ` 1` .
+    See the description of [`cqtx`](#cqtx) for behaviour in reverse proxy mode.
 
 `cquc`
 :   The client request canonical URL. This differs from `cqu` in that blanks 
(and 
@@ -121,15 +117,11 @@ Notice:    Licensed to the Apache Softwa
     by escape sequences. The escape sequence is a percentage sign followed by 
the 
     ASCII code number in hex.
  
-     In reverse proxy mode, Traffic Server logs the rewritten/mapped URL 
(according 
-    to the rules in the `remap.config` file), and _not_ the pristine/unmapped 
-    URL. To configure Traffic Server to log the original (unmapped) URL, set 
the 
-    _`proxy.config.url_remap.pristine_host_hdr`_ variable in the 
`records.config` 
-    file to ` 1` .
+    See the description of [`cqtx`](#cqtx) for behaviour in reverse proxy mode.
 
 `cqup`
 :    The client request URL path; specifies the argument portion of the URL 
(everything after the host).
-     For example, if the URL is ` http://www.company.com/images/x.gif` , then 
this field displays ` /images/x.gif`
+     For example, if the URL is `http://www.company.com/images/x.gif`, then 
this field displays `/images/x.gif`
 
 `cqus`
 :   The client request URL scheme.

Modified: 
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/security-options/index.en.mdtext
URL: 
http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/security-options/index.en.mdtext?rev=1103947&r1=1103946&r2=1103947&view=diff
==============================================================================
--- 
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/security-options/index.en.mdtext
 (original)
+++ 
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/security-options/index.en.mdtext
 Mon May 16 23:01:38 2011
@@ -190,7 +190,7 @@ and origin server connections, you must 
       the server with which it is communicating, thereby enabling exchange of 
encryption keys.
  
 
-##### To configure SSL termination for Traffic Server/origin server 
connections:  ##### {#configureSSLterminationforTS/originserverconnections}
+##### To configure SSL termination for Traffic Server/origin server 
connections:  ##### {#configureSSLterminationforTSoriginserverconnections}
 
 2. Edit the following variables in the `SSL Termination` section of the 
`records.config` file: 
     * 
[_`proxy.config.ssl.auth.enabled`_](../configuration-files/records.config#proxy.config.ssl.auth.enabled)

Modified: 
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/traffic-line-commands/index.en.mdtext
URL: 
http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/traffic-line-commands/index.en.mdtext?rev=1103947&r1=1103946&r2=1103947&view=diff
==============================================================================
--- 
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/traffic-line-commands/index.en.mdtext
 (original)
+++ 
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/traffic-line-commands/index.en.mdtext
 Mon May 16 23:01:38 2011
@@ -37,52 +37,52 @@ path, then prepend the Traffic Line comm
 
 The following list describes all the commands available in Traffic Line.
 
-`traffic_line -b`
+`-b`
 :    Bounces Traffic Server on the local node. Bouncing Traffic Server shuts 
down
      and immediately restarts the Traffic Server node.
 
-`traffic_line -c`
+`-c`
 :    Clears accumulated statistics on the local node.
 
-`traffic_line -h`
+`-h`
 :    Displays a list of Traffic Line commands.
 
-`traffic_line -p` _`socket_path`_
+`-p` _`socket_path`_
 :    Specifies location (directory and path) of the socket used for Traffic 
Line communication.  
      The default path is: _`install_dir`_`/config/cli`
 
-`traffic_line -r _variable_`
+`-r _variable_`
 :   Displays specific performance statistics or a current configuration 
setting.
     For a list of the variables you can specify, see [Traffic Line 
Variables](#TrafficLineVariables).
 
-`traffic_line -s` _`variable`_ `-v` _`value`_
+`-s` _`variable`_ `-v` _`value`_
 :   Sets configuration variables, where _`variable`_ is the configuration 
variable
     you want to change and _`value`_ is the value you want to set. Refer to 
[records.config](../configuration-files/records.config)
     for a list of the configuration variables you can specify.
 
-`traffic_line -x`
+`-x`
 :   Initiates a Traffic Server configuration file reread. Use this command 
after
     every configuration file modification.
 
-`traffic_line -B`
+`-B`
 :   Bounces all Traffic Server nodes in the cluster. Bouncing Traffic Server 
shuts
     down and immediately restarts Traffic Server, node-by-node.
 
-`traffic_line -C`
+`-C`
 :   Clears accumulated statistics on all nodes in the cluster.
 
-`traffic_line -L`
+`-L`
 :   Restarts the `traffic_manager` and `traffic_server` processes on the local
     node.
 
-`traffic_line -M`
+`-M`
 :   Restarts the `traffic_manager` process and the `traffic_server` process
     on all the nodes in a cluster.
 
-`traffic_line -S`
+`-S`
 :   Shuts down Traffic Server on the local node.
 
-`traffic_line -U`
+`-U`
 :   Starts Traffic Server on the local node.
 
 
@@ -308,6 +308,7 @@ DNS successes
 
 Bytes read
 :     _`proxy.process.cluster.read_bytes`_
+
 Bytes written
 :     _`proxy.process.cluster.write_bytes`_
 
@@ -344,13 +345,11 @@ Number of error events logged
 
 ### Congestion Control ### {#TLVarsCongestionControl}
 
-Number of congestions Traffic Server has observed because the maximum number
-of connections was exceeded.
+Number of congestions Traffic Server has observed because the maximum number 
of connections was exceeded.
 :   _`proxy.process.congestion.congested_on_max_connection`_
 
 
 
-Number of congestions Traffic Server has observed because of an OS response
-or timeout failure.
+Number of congestions Traffic Server has observed because of an OS response or 
timeout failure.
 :   _`proxy.process.congestion.congested_on_conn_failures`_
 

Modified: 
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/traffic-server-error-messages/index.en.mdtext
URL: 
http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/traffic-server-error-messages/index.en.mdtext?rev=1103947&r1=1103946&r2=1103947&view=diff
==============================================================================
--- 
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/traffic-server-error-messages/index.en.mdtext
 (original)
+++ 
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/traffic-server-error-messages/index.en.mdtext
 Mon May 16 23:01:38 2011
@@ -36,8 +36,6 @@ occur and which might require your atten
 
 ###  Traffic Server Process Fatal ### {#TSProcessFatal}
 
-**Message**  **Description**
-
 `Accept port is not between 1 and 65535. Please check configuration`
 :   The port specified in the `records.config` file that accepts incoming HTTP
     requests is not valid.
@@ -94,7 +92,7 @@ _`Logfile`_ `error:` _`error_number`_
 `No cache disks specified in storage.config file: cache disabled`
 :   The Traffic Server `storage.config` file does not list any cache disks; 
Traffic
     Server is running in proxy-only mode. You must add the disks you want to 
use
-    for the cache to the [storage.config](files.htm#storage.config) file.
+    for the cache to the 
[storage.config](../configuration-files/storage.config) file.
 
 
 ## Traffic Server Alarm Messages ## {#TSAlarmMessages}
@@ -140,7 +138,7 @@ _`Logfile`_ `error:` _`error_number`_
 
 `Traffic Server failed to parse line` _`line_number`_ `of the logging config 
file` _`filename`_
 :   Check your custom log configuration file; there could be syntax errors. 
Refer
-    to [ Custom Logging Fields](logfmts.htm#66912) for correct custom log 
format
+    to [Custom Logging Fields](logfmts.htm#66912) for correct custom log format
     fields.
 
 `vip_config binary is not setuid root, manager will be unable to enable 
virtual ip addresses`


Reply via email to