You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficserver.apache.org by bu...@apache.org on 2011/03/08 18:47:27 UTC

svn commit: r786691 - /websites/staging/trafficserver/trunk/content/docs/trunk/admin/traffic-line-commands/index.en.html

Author: buildbot
Date: Tue Mar  8 17:47:27 2011
New Revision: 786691

Log:
Staging update by buildbot

Modified:
    websites/staging/trafficserver/trunk/content/docs/trunk/admin/traffic-line-commands/index.en.html

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/traffic-line-commands/index.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/traffic-line-commands/index.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/traffic-line-commands/index.en.html Tue Mar  8 17:47:27 2011
@@ -27,11 +27,9 @@
     
       <div class="nav">
       
-        <span class="nav"><a href="../index.en.html">Top</a></span>
-      
         <span class="nav"><a href="../event-logging-formats/index.en.html">Next</a></span>
       
-        <span class="nav"><a href="../working-log-files/index.en.html">Back</a></span>
+        <span class="nav"><a href="../sdk/index.en.html">SDK</a></span>
       
       </div>
     
@@ -39,453 +37,251 @@
   <div class="main">
     
     <div id="content">
-      <h1 id="AppendixC-TrafficLineCommands">Appendix C - Traffic Line Commands</h1>
-<p>This appendix contains the following sections: </p>
+      <h1 id="TrafficLineCommands">Traffic Line Commands</h1>
+<p>This section contains the following sections:</p>
 <ul>
-<li><a href="#1053987">Traffic Line Commands</a></li>
-<li><a href="#1025718">Traffic Line Variables</a></li>
+<li><a href="#TrafficLineCommands">Traffic Line Commands</a></li>
+<li><a href="#TrafficLineVariables">Traffic Line Variables</a></li>
 </ul>
-<h2 id="TrafficLineCommands">Traffic Line Commands</h2>
-<p>Use Traffic Line to execute individual Traffic Server commands and to script 
-multiple commands in a shell. Execute Traffic Line commands from the Traffic 
-Server <code>bin</code> directory. If the Traffic Server <code>bin</code> directory is not in your 
-path, then prepend the Traffic Line command with <code>./</code> (for example: <code>./traffic_line 
--p</code>). </p>
-<p>The following table describes all the commands available in Traffic Line. </p>
-<div class="codehilite"><pre>  <span class="o">**</span>
-</pre></div>
-
-
-<p>Command</p>
-<hr />
-<p>Description</p>
-<p>** </p>
-<dl>
-<dt><code>traffic_line -b</code> </dt>
-<dd>
-<p>Bounces Traffic Server on the local node. Bouncing Traffic Server shuts down 
-and immediately restarts the Traffic Server node.</p>
-</dd>
-<dt><code>traffic_line -c</code> </dt>
-<dd>
-<p>Clears accumulated statistics on the local node.</p>
-</dd>
-<dt><code>traffic_line -h</code> </dt>
-<dd>
-<p>Displays a list of Traffic Line commands.</p>
-</dd>
-<dt><code>traffic_line -p _socket_path_</code> </dt>
-<dd>
-<p>Specifies location (directory and path) of the socket used for Traffic Line communication.<br />
- The default path is: <code>_install_dir_ /config/cli</code> </p>
-</dd>
-<dt><code>traffic_line -q</code> </dt>
-<dd>
-<p>Displays a list of the origin servers that are currently congested. </p>
-<p><strong>Note:</strong> To use this command, you must set the variable <code>_proxy.config.raf.enabled_</code> 
-to 1 and set the variable <code>_proxy.config.raf.port_</code> to a different port _ 
-only_ if there is a conflict with the default port 9000.</p>
-</dd>
-<dt><code>traffic_line -r _variable_</code> </dt>
-<dd>
-<p>Displays specific performance statistics or a current configuration setting. 
-For a list of the variables you can specify, see <a href="cli.htm#1025718">Traffic Line Variables</a>. </p>
-</dd>
-<dt><code>traffic_line -s _variable_ -v _value_</code> </dt>
-<dd>
-<p>Sets configuration variables, where <code>_variable_</code> is the configuration variable 
-you want to change and <code>_value_</code> is the value you want to set. Refer to <a href="files.htm#records.config">records.config</a> 
-for a list of the configuration variables you can specify.</p>
-</dd>
-<dt><code>traffic_line -x</code> </dt>
-<dd>
-<p>Initiates a Traffic Server configuration file reread. Use this command after 
-every configuration file modification.</p>
-</dd>
-<dt><code>traffic_line -B</code> </dt>
-<dd>
-<p>Bounces all Traffic Server nodes in the cluster. Bouncing Traffic Server shuts 
-down and immediately restarts Traffic Server, node-by-node.</p>
-</dd>
-<dt><code>traffic_line -C</code> </dt>
-<dd>
-<p>Clears accumulated statistics on all nodes in the cluster.</p>
-</dd>
-<dt><code>traffic_line -L</code> </dt>
-<dd>
-<p>Restarts the <code>traffic_manager</code> and <code>traffic_server</code> processes on the local 
-node.</p>
-</dd>
-<dt><code>traffic_line -M</code> </dt>
-<dd>
-<p>Restarts the <code>traffic_manager</code> process and the <code>traffic_server</code> process 
-on all the nodes in a cluster.</p>
-</dd>
-<dt><code>traffic_line -S</code> </dt>
-<dd>
-<p>Shuts down Traffic Server on the local node.</p>
-</dd>
-<dt><code>traffic_line -U</code> </dt>
-<dd>
-<p>Starts Traffic Server on the local node.</p>
-<div class="codehilite"><pre><span class="o">**</span><span class="n">Traffic</span> <span class="n">Line</span> <span class="n">Variables</span><span class="o">**</span>
-</pre></div>
-
-
-</dd>
-</dl>
-<p>You can view statistics and change configuration options in Traffic Line by 
-using specific variables. The variables used for gathering statistics are described 
-below. The variables used for viewing and changing configuration options are 
-described in <a href="files.htm#records.config">records.config</a>. For procedures about 
-specifying the variables, refer to <a href="monitor.htm">Viewing Statistics from Traffic Line</a> 
-and <a href="configure.htm">Configuring Traffic Server Using Traffic Line</a>. </p>
-<p>The variables used for viewing individual statistics are described in the 
-following table. To view a statistic in Traffic Line, enter the command <code>traffic_line 
--r _variable_</code>at the prompt. </p>
-<dl>
-<dt><strong> Statistic</strong></dt>
-<dd>
-<p><strong> Variable</strong></p>
-</dd>
-</dl>
-<p><strong> Summary</strong></p>
+<h2 id="TrafficLineCommands_1">Traffic Line Commands</h2>
+<p>Use Traffic Line to execute individual Traffic Server commands and to script
+multiple commands in a shell. Execute Traffic Line commands from the Traffic
+Server <code>bin</code> directory. If the Traffic Server <code>bin</code> directory is not in your
+path, then prepend the Traffic Line command with <code>./</code> (for example:
+<code>./traffic_line  -p</code>).</p>
+<p>The following list describes all the commands available in Traffic Line.</p>
+<dl>
+<dt><code>traffic_line -b</code></dt>
+<dd>Bounces Traffic Server on the local node. Bouncing Traffic Server shuts down
+ and immediately restarts the Traffic Server node.</dd>
+<dt><code>traffic_line -c</code></dt>
+<dd>Clears accumulated statistics on the local node.</dd>
+<dt><code>traffic_line -h</code></dt>
+<dd>Displays a list of Traffic Line commands.</dd>
+<dt><code>traffic_line -p</code> <em><code>socket_path</code></em></dt>
+<dd>Specifies location (directory and path) of the socket used for Traffic Line communication.<br />
+ The default path is: <em><code>install_dir</code></em><code>/config/cli</code></dd>
+<dt><code>traffic_line -q</code></dt>
+<dd>Displays a list of the origin servers that are currently congested.</dd>
+</dl>
+<p><strong>Note:</strong> To use this command, you must set the variable <em><code>proxy.config.raf.enabled</code></em>
+    to <code>1</code> and set the variable <em><code>proxy.config.raf.port</code></em> to a different port
+    <em>only</em> if there is a conflict with the default port <code>9000</code>.</p>
+<dl>
+<dt><code>traffic_line -r _variable_</code></dt>
+<dd>Displays specific performance statistics or a current configuration setting.
+For a list of the variables you can specify, see <a href="cli.htm#1025718">Traffic Line Variables</a>.</dd>
+<dt><code>traffic_line -s</code> <em><code>variable</code></em> <code>-v</code> <em><code>value</code></em></dt>
+<dd>Sets configuration variables, where <em><code>variable</code></em> is the configuration variable
+you want to change and <em><code>value</code></em> is the value you want to set. Refer to <a href="../configuration-files/records.config">records.config</a>
+for a list of the configuration variables you can specify.</dd>
+<dt><code>traffic_line -x</code></dt>
+<dd>Initiates a Traffic Server configuration file reread. Use this command after
+every configuration file modification.</dd>
+<dt><code>traffic_line -B</code></dt>
+<dd>Bounces all Traffic Server nodes in the cluster. Bouncing Traffic Server shuts
+down and immediately restarts Traffic Server, node-by-node.</dd>
+<dt><code>traffic_line -C</code></dt>
+<dd>Clears accumulated statistics on all nodes in the cluster.</dd>
+<dt><code>traffic_line -L</code></dt>
+<dd>Restarts the <code>traffic_manager</code> and <code>traffic_server</code> processes on the local
+node.</dd>
+<dt><code>traffic_line -M</code></dt>
+<dd>Restarts the <code>traffic_manager</code> process and the <code>traffic_server</code> process
+on all the nodes in a cluster.</dd>
+<dt><code>traffic_line -S</code></dt>
+<dd>Shuts down Traffic Server on the local node.</dd>
+<dt><code>traffic_line -U</code></dt>
+<dd>Starts Traffic Server on the local node.</dd>
+</dl>
+<h1 id="TrafficLineVariables">Traffic Line Variables</h1>
+<p>You can view statistics and change configuration options in Traffic Line by
+using specific variables. The variables used for gathering statistics are described
+below. The variables used for viewing and changing configuration options are
+described in <a href="files.htm#records.config">records.config</a>. For procedures about
+specifying the variables, refer to <a href="monitor.htm">Viewing Statistics from Traffic Line</a>
+and <a href="configure.htm">Configuring Traffic Server Using Traffic Line</a>.</p>
+<p>The variables used for viewing individual statistics are described in the
+following table. To view a statistic in Traffic Line, enter the command
+<code>traffic_line -r</code> <em><code>variable</code></em> at the prompt.</p>
+<h3 id="TLVarsSummary">Summary</h3>
 <dl>
 <dt>Node name</dt>
-<dd>
-<p>_<code>proxy.node.hostname</code> _</p>
-</dd>
+<dd><em><code>proxy.node.hostname</code></em></dd>
 <dt>Objects served</dt>
-<dd>
-<p>_<code>proxy.node.user_agents_total_documents_served</code> _</p>
-</dd>
+<dd><em><code>proxy.node.user_agents_total_documents_served</code></em></dd>
 <dt>Transactions per second</dt>
-<dd>
-<p>_<code>proxy.node.user_agent_xacts_per_second</code> _</p>
-</dd>
-</dl>
-<p><strong> Node</strong></p>
-<dl>
-<dt>Document hit rate </dt>
-<dd>
-<p>_<code>proxy.node.cache_hit_ratio_avg_10s</code> _</p>
-<p>_<code>proxy.cluster.cache_hit_ratio_avg_10s</code> _</p>
-</dd>
-<dt>Bandwidth savings </dt>
-<dd>
-<p>_<code>proxy.node.bandwidth_hit_ratio_avg_10s</code> _</p>
-<p>_<code>proxy.cluster.bandwidth_hit_ratio_avg_10s</code> _</p>
-</dd>
+<dd><em><code>proxy.node.user_agent_xacts_per_second</code></em></dd>
+</dl>
+<h3 id="TLVarsNode">Node</h3>
+<dl>
+<dt>Document hit rate</dt>
+<dd><em><code>proxy.node.cache_hit_ratio_avg_10s</code></em></dd>
+<dd><em><code>proxy.cluster.cache_hit_ratio_avg_10s</code></em></dd>
+<dt>Bandwidth savings</dt>
+<dd><em><code>proxy.node.bandwidth_hit_ratio_avg_10s</code></em></dd>
+<dd><em><code>proxy.cluster.bandwidth_hit_ratio_avg_10s</code></em></dd>
 <dt>Cache percent free</dt>
-<dd>
-<p>_<code>proxy.node.cache.percent_free</code> _</p>
-<p>_<code>proxy.cluster.cache.percent_free</code> _</p>
-</dd>
+<dd><em><code>proxy.node.cache.percent_free</code></em></dd>
+<dd><em><code>proxy.cluster.cache.percent_free</code></em></dd>
 <dt>Open origin server connections</dt>
-<dd>
-<p>_<code>proxy.node.current_server_connections</code> _</p>
-<p>_<code>proxy.cluster.current_server_connections</code> _</p>
-</dd>
-<dt>Open client connections </dt>
-<dd>
-<p>_<code>proxy.node.current_client_connections</code> _</p>
-<p>_<code>proxy.cluster.current_client_connections</code> _</p>
-</dd>
-<dt>Cache transfers in progress </dt>
-<dd>
-<p>_<code>proxy.node.current_cache_connections</code> _</p>
-<p>_<code>proxy.cluster.current_cache_connections</code> _</p>
-</dd>
+<dd><em><code>proxy.node.current_server_connections</code></em></dd>
+<dd><em><code>proxy.cluster.current_server_connections</code></em></dd>
+<dt>Open client connections</dt>
+<dd><em><code>proxy.node.current_client_connections</code></em></dd>
+<dd><em><code>proxy.cluster.current_client_connections</code></em></dd>
+<dt>Cache transfers in progress</dt>
+<dd><em><code>proxy.node.current_cache_connections</code></em></dd>
+<dd><em><code>proxy.cluster.current_cache_connections</code></em></dd>
 <dt>Client throughput (Mbits/sec)</dt>
-<dd>
-<p>_<code>proxy.node.client_throughput_out</code> _</p>
-<p>_<code>proxy.cluster.client_throughput_out</code> _</p>
-</dd>
-<dt>Transactions per second </dt>
-<dd>
-<p>_<code>proxy.node.user_agent_xacts_per_second</code> _</p>
-<p>_<code>proxy.cluster.user_agent_xacts_per_second</code> _</p>
-</dd>
-<dt>DNS lookups per second </dt>
-<dd>
-<p>_<code>proxy.node.dns.lookups_per_second</code> _</p>
-<p>_<code>proxy.cluster.dns.lookups_per_second</code> _</p>
-</dd>
-<dt>Host database hit rate </dt>
-<dd>
-<p>_<code>proxy.node.hostdb.hit_ratio_avg_10s</code> _</p>
-<p>_<code>proxy.cluster.hostdb.hit_ratio_avg_10s</code> _</p>
-</dd>
+<dd><em><code>proxy.node.client_throughput_out</code></em></dd>
+<dd><em><code>proxy.cluster.client_throughput_out</code></em></dd>
+<dt>Transactions per second</dt>
+<dd><em><code>proxy.node.user_agent_xacts_per_second</code></em></dd>
+<dd><em><code>proxy.cluster.user_agent_xacts_per_second</code></em></dd>
+<dt>DNS lookups per second</dt>
+<dd><em><code>proxy.node.dns.lookups_per_second</code></em></dd>
+<dd><em><code>proxy.cluster.dns.lookups_per_second</code></em></dd>
+<dt>Host database hit rate</dt>
+<dd><em><code>proxy.node.hostdb.hit_ratio_avg_10s</code></em></dd>
+<dd><em><code>proxy.cluster.hostdb.hit_ratio_avg_10s</code></em></dd>
 </dl>
-<p><strong> HTTP</strong></p>
+<h3 id="TLVarsHTTP">HTTP</h3>
 <dl>
 <dt>Total document bytes from client</dt>
-<dd>
-<p>_<code>proxy.process.http.user_agent_response_document_total_size</code> _</p>
-</dd>
+<dd><em><code>proxy.process.http.user_agent_response_document_total_size</code></em></dd>
 <dt>Total header bytes from client</dt>
-<dd>
-<p>_<code>proxy.process.http.user_agent_response_header_total_size</code> _</p>
-</dd>
+<dd><em><code>proxy.process.http.user_agent_response_header_total_size</code></em></dd>
 <dt>Total connections to client</dt>
-<dd>
-<p>_<code>proxy.process.http.total_client_connections</code> _</p>
-</dd>
+<dd><em><code>proxy.process.http.total_client_connections</code></em></dd>
 <dt>Client transactions in progress</dt>
-<dd>
-<p>_<code>proxy.process.http.current_client_transactions</code> _</p>
-</dd>
+<dd><em><code>proxy.process.http.current_client_transactions</code></em></dd>
 <dt>Total document bytes from origin server</dt>
-<dd>
-<p>_<code>proxy.process.http.origin_server_response_document_total_size</code> _</p>
-</dd>
+<dd><em><code>proxy.process.http.origin_server_response_document_total_size</code></em></dd>
 <dt>Total header bytes from origin server</dt>
-<dd>
-<p>_<code>proxy.process.http.origin_server_response_header_total_size</code> _</p>
-</dd>
+<dd><em><code>proxy.process.http.origin_server_response_header_total_size</code></em></dd>
 <dt>Total connections to origin server</dt>
-<dd>
-<p>_<code>proxy.process.http.total_server_connections</code> _</p>
-</dd>
-<dt>Origin server transactions in progress </dt>
-<dd>
-<p>_<code>proxy.process.http.current_server_transactions</code> _</p>
-</dd>
+<dd><em><code>proxy.process.http.total_server_connections</code></em></dd>
+<dt>Origin server transactions in progress</dt>
+<dd><em><code>proxy.process.http.current_server_transactions</code></em></dd>
 </dl>
-<p><strong> ICP</strong></p>
+<h3 id="TLVarsICP">ICP</h3>
 <dl>
 <dt>ICP query requests originating from this node</dt>
-<dd>
-<p>_<code>proxy.process.icp.icp_query_requests</code> _</p>
-</dd>
+<dd><em><code>proxy.process.icp.icp_query_requests</code></em></dd>
 <dt>ICP query messages sent from this node</dt>
-<dd>
-<p>_<code>proxy.process.icp.total_udp_send_queries</code> _</p>
-</dd>
+<dd><em><code>proxy.process.icp.total_udp_send_queries</code></em></dd>
 <dt>ICP peer hit messages received from this node</dt>
-<dd>
-<p>_<code>proxy.process.icp.icp_query_hits</code> _</p>
-</dd>
-<dt>ICP peer miss messages received from this node </dt>
-<dd>
-<p>_<code>proxy.process.icp.icp_query_misses</code> _</p>
-</dd>
+<dd><em><code>proxy.process.icp.icp_query_hits</code></em></dd>
+<dt>ICP peer miss messages received from this node</dt>
+<dd><em><code>proxy.process.icp.icp_query_misses</code></em></dd>
 <dt>Total ICP responses received from this node</dt>
-<dd>
-<p>_<code>proxy.process.icp.icp_remote_responses</code> _</p>
-</dd>
+<dd><em><code>proxy.process.icp.icp_remote_responses</code></em></dd>
 <dt>Average ICP message response time (ms) from this node</dt>
-<dd>
-<p>_<code>proxy.process.icp.total_icp_response_time</code> _</p>
-</dd>
+<dd><em><code>proxy.process.icp.total_icp_response_time</code></em></dd>
 <dt>Average ICP request time (ms) from this node</dt>
-<dd>
-<p>_<code>proxy.process.icp.total_icp_request_time</code> _</p>
-</dd>
+<dd><em><code>proxy.process.icp.total_icp_request_time</code></em></dd>
 <dt>Query messages received from ICP peers</dt>
-<dd>
-<p>_<code>proxy.process.icp.icp_remote_query_requests</code> _</p>
-</dd>
+<dd><em><code>proxy.process.icp.icp_remote_query_requests</code></em></dd>
 <dt>Remote query hits from ICP peers</dt>
-<dd>
-<p>_<code>proxy.process.icp.cache_lookup_success</code> _</p>
-</dd>
+<dd><em><code>proxy.process.icp.cache_lookup_success</code></em></dd>
 <dt>Remote query misses from ICP peers</dt>
-<dd>
-<p>_<code>proxy.process.icp.cache_lookup_fail</code> _</p>
-</dd>
+<dd><em><code>proxy.process.icp.cache_lookup_fail</code></em></dd>
 <dt>Successful response messages sent to peers</dt>
-<dd>
-<p>_<code>proxy.process.icp.query_response_write</code> _</p>
-</dd>
+<dd><em><code>proxy.process.icp.query_response_write</code></em></dd>
 </dl>
-<p><strong> Cache </strong></p>
+<h3 id="TLVarsCache">Cache</h3>
 <dl>
 <dt>Bytes used</dt>
-<dd>
-<p>_<code>proxy.process.cache.bytes_used</code> _</p>
-</dd>
+<dd><em><code>proxy.process.cache.bytes_used</code></em></dd>
 <dt>Cache size</dt>
-<dd>
-<p>_<code>proxy.process.cache.bytes_total</code> _</p>
-</dd>
+<dd><em><code>proxy.process.cache.bytes_total</code></em></dd>
 <dt>Lookups in progress</dt>
-<dd>
-<p>_<code>proxy.process.cache.lookup.active</code> _</p>
-</dd>
+<dd><em><code>proxy.process.cache.lookup.active</code></em></dd>
 <dt>Lookups completed</dt>
-<dd>
-<p>_<code>proxy.process.cache.lookup.success</code> _</p>
-</dd>
+<dd><em><code>proxy.process.cache.lookup.success</code></em></dd>
 <dt>Lookup misses</dt>
-<dd>
-<p>_<code>proxy.process.cache.lookup.failure</code> _</p>
-</dd>
+<dd><em><code>proxy.process.cache.lookup.failure</code></em></dd>
 <dt>Reads in progress</dt>
-<dd>
-<p>_<code>proxy.process.cache.read.active</code> _</p>
-</dd>
+<dd><em><code>proxy.process.cache.read.active</code></em></dd>
 <dt>Reads completed</dt>
-<dd>
-<p>_<code>proxy.process.cache.read.success</code> _</p>
-</dd>
+<dd><em><code>proxy.process.cache.read.success</code></em></dd>
 <dt>Read misses</dt>
-<dd>
-<p>_<code>proxy.process.cache.read.failure</code> _</p>
-</dd>
+<dd><em><code>proxy.process.cache.read.failure</code></em></dd>
 <dt>Writes in progress</dt>
-<dd>
-<p>_<code>proxy.process.cache.write.active</code> _</p>
-</dd>
+<dd><em><code>proxy.process.cache.write.active</code></em></dd>
 <dt>Writes completed</dt>
-<dd>
-<p>_<code>proxy.process.cache.write.success</code> _</p>
-</dd>
+<dd><em><code>proxy.process.cache.write.success</code></em></dd>
 <dt>Write failures</dt>
-<dd>
-<p>_<code>proxy.process.cache.write.failure</code> _</p>
-</dd>
+<dd><em><code>proxy.process.cache.write.failure</code></em></dd>
 <dt>Updates in progress</dt>
-<dd>
-<p>_<code>proxy.process.cache.update.active</code> _</p>
-</dd>
+<dd><em><code>proxy.process.cache.update.active</code></em></dd>
 <dt>Updates completed</dt>
-<dd>
-<p>_<code>proxy.process.cache.update.success</code> _</p>
-</dd>
+<dd><em><code>proxy.process.cache.update.success</code></em></dd>
 <dt>Update failures</dt>
-<dd>
-<p>_<code>proxy.process.cache.update.failure</code> _</p>
-</dd>
+<dd><em><code>proxy.process.cache.update.failure</code></em></dd>
 <dt>Removes in progress</dt>
-<dd>
-<p>_<code>proxy.process.cache.remove.active</code> _</p>
-</dd>
+<dd><em><code>proxy.process.cache.remove.active</code></em></dd>
 <dt>Remove successes</dt>
-<dd>
-<p>_<code>proxy.process.cache.remove.success</code> _</p>
-</dd>
+<dd><em><code>proxy.process.cache.remove.success</code></em></dd>
 <dt>Remove failures</dt>
-<dd>
-<p>_<code>proxy.process.cache.remove.failure</code> _</p>
-</dd>
+<dd><em><code>proxy.process.cache.remove.failure</code></em></dd>
 </dl>
-<p><strong> Host Database</strong> </p>
+<h3 id="TLVarsHostDatabase">Host Database</h3>
 <dl>
 <dt>Total lookups</dt>
-<dd>
-<p>_<code>proxy.process.hostdb.total_lookups</code> _</p>
-</dd>
+<dd><em><code>proxy.process.hostdb.total_lookups</code></em></dd>
 <dt>Total hits</dt>
-<dd>
-<p>_<code>proxy.process.hostdb.total_hits</code> _</p>
-</dd>
+<dd><em><code>proxy.process.hostdb.total_hits</code></em></dd>
 <dt>Time TTL (min)</dt>
-<dd>
-<p>_<code>proxy.process.hostdb.ttl</code> _</p>
-</dd>
+<dd><em><code>proxy.process.hostdb.ttl</code></em></dd>
 </dl>
-<p><strong> DNS</strong> </p>
+<h3 id="TLVarsDNS">DNS</h3>
 <dl>
 <dt>DNS total lookups</dt>
-<dd>
-<p>_<code>proxy.process.dns.total_dns_lookups</code> _</p>
-</dd>
+<dd><em><code>proxy.process.dns.total_dns_lookups</code></em></dd>
 <dt>Average lookup time (msec)</dt>
-<dd>
-<p>_<code>proxy.process.dns.lookup_avg_time</code> _</p>
-</dd>
+<dd><em><code>proxy.process.dns.lookup_avg_time</code></em></dd>
 <dt>DNS successes</dt>
-<dd>
-<p>_<code>proxy.process.dns.lookup_successes</code> _</p>
-</dd>
+<dd><em><code>proxy.process.dns.lookup_successes</code></em></dd>
 </dl>
-<p><strong> Cluster </strong></p>
+<h3 id="TLVarsCluster">Cluster</h3>
 <dl>
 <dt>Bytes read</dt>
-<dd>
-<p>_<code>proxy.process.cluster.read_bytes</code> _</p>
-</dd>
+<dd><em><code>proxy.process.cluster.read_bytes</code></em></dd>
 <dt>Bytes written</dt>
-<dd>
-<p>_<code>proxy.process.cluster.write_bytes</code> _</p>
-</dd>
+<dd><em><code>proxy.process.cluster.write_bytes</code></em></dd>
 <dt>Connections open</dt>
-<dd>
-<p>_<code>proxy.process.cluster.connections_open</code> _</p>
-</dd>
+<dd><em><code>proxy.process.cluster.connections_open</code></em></dd>
 <dt>Total operations</dt>
-<dd>
-<p>_<code>proxy.process.cluster.connections_opened</code> _</p>
-</dd>
+<dd><em><code>proxy.process.cluster.connections_opened</code></em></dd>
 <dt>Network backups</dt>
-<dd>
-<p>_<code>proxy.process.cluster.net_backup</code> _</p>
-</dd>
+<dd><em><code>proxy.process.cluster.net_backup</code></em></dd>
 <dt>Clustering nodes</dt>
-<dd>
-<p>_<code>proxy.process.cluster.nodes</code> _</p>
-</dd>
+<dd><em><code>proxy.process.cluster.nodes</code></em></dd>
 </dl>
-<p><strong> Logging </strong></p>
+<h3 id="TLVarsLogging">Logging</h3>
 <dl>
 <dt>Log files currently open</dt>
-<dd>
-<p>_<code>proxy.process.log.log_files_open</code> _</p>
-</dd>
+<dd><em><code>proxy.process.log.log_files_open</code></em></dd>
 <dt>Space used for log files</dt>
-<dd>
-<p>_<code>proxy.process.log.log_files_space_used</code> _</p>
-</dd>
+<dd><em><code>proxy.process.log.log_files_space_used</code></em></dd>
 <dt>Number of access events logged</dt>
-<dd>
-<p>_<code>proxy.process.log.event_log_access</code> _</p>
-</dd>
+<dd><em><code>proxy.process.log.event_log_access</code></em></dd>
 <dt>Number of access events skipped</dt>
-<dd>
-<p>_<code>proxy.process.log.event_log_access_skip</code> _</p>
-</dd>
+<dd><em><code>proxy.process.log.event_log_access_skip</code></em></dd>
 <dt>Number of error events logged</dt>
-<dd>
-<p>_<code>proxy.process.log.event_log_error</code> _</p>
-</dd>
+<dd><em><code>proxy.process.log.event_log_error</code></em></dd>
 </dl>
-<p><strong> Congestion Control</strong></p>
+<h3 id="congestion_control__tlvarscongestion_control">Congestion Control ### {#TLVarsCongestion Control}</h3>
 <dl>
-<dt>Number of congestions Traffic Server has observed because the maximum number </dt>
+<dt>Number of congestions Traffic Server has observed because the maximum number</dt>
 <dt>of connections was exceeded.</dt>
-<dd>
-<p><em><code>proxy.process.congestion.congested_on_max_connection</code></em></p>
-</dd>
-<dt>Number of congestions Traffic Server has observed because of an OS response </dt>
+<dd><em><code>proxy.process.congestion.congested_on_max_connection</code></em></dd>
+<dt>Number of congestions Traffic Server has observed because of an OS response</dt>
 <dt>or timeout failure.</dt>
-<dd>
-<p><em><code>proxy.process.congestion.congested_on_conn_failures</code></em></p>
-</dd>
+<dd><em><code>proxy.process.congestion.congested_on_conn_failures</code></em></dd>
 </dl>
-<ul>
-<li><a href="intro.htm">Overview</a></li>
-<li><a href="getstart.htm">Getting Started</a></li>
-<li><a href="http.htm">HTTP Proxy Caching </a></li>
-<li><a href="explicit.htm">Explicit Proxy Caching</a></li>
-<li><a href="reverse.htm">Reverse Proxy and HTTP Redirects</a></li>
-<li><a href="hier.htm">Hierarchical Caching</a></li>
-<li><a href="cache.htm">Configuring the Cache</a></li>
-<li><a href="monitor.htm">Monitoring Traffic</a></li>
-<li><a href="configure.htm">Configuring Traffic Server</a></li>
-<li><a href="secure.htm">Security Options</a></li>
-<li><a href="log.htm">Working with Log Files</a></li>
-<li><a href="cli.htm">Traffic Line Commands</a></li>
-<li><a href="logfmts.htm">Event Logging Formats</a></li>
-<li><a href="files.htm">Configuration Files</a> </li>
-<li><a href="errors.htm">Traffic Server Error Messages</a></li>
-<li><a href="trouble.htm">FAQ and Troubleshooting Tips</a></li>
-<li><a href="ts_admin_chinese.pdf">Traffic Server 管理员指南</a> (PDF)</li>
-</ul>
-<p>Copyright © 2011 <a href="http://www.apache.org/">The Apache Software Foundation</a>. 
-Licensed under the <a href="http://www.apache.org/licenses/">Apache License</a>, Version 
-2.0. Apache Traffic Server, Apache, the Apache Traffic Server logo, and the 
-Apache feather logo are trademarks of The Apache Software Foundation.</p>
     </div>
   </div><!-- main -->