trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iga...@apache.org
Subject svn commit: r1132938 - in /trafficserver/site/branches/ats-cms/content/docs/trunk/admin: configuration-files/ configuring-cache/ hierachical-caching/
Date Tue, 07 Jun 2011 10:05:47 GMT
Author: igalic
Date: Tue Jun  7 10:05:46 2011
New Revision: 1132938

URL: http://svn.apache.org/viewvc?rev=1132938&view=rev
Log:
Fixing up the Configuring Cache chapter.
Renaming partition.config to volume.config and most references to it.

Added:
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/volume.config.en.mdtext
      - copied, changed from r1132908, trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/partition.config.en.mdtext
Removed:
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/partition.config.en.mdtext
Modified:
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/hosting.config.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/order.txt
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuring-cache/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/hierachical-caching/index.en.mdtext

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/hosting.config.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/hosting.config.en.mdtext?rev=1132938&r1=1132937&r2=1132938&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/hosting.config.en.mdtext
(original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/hosting.config.en.mdtext
Tue Jun  7 10:05:46 2011
@@ -25,17 +25,17 @@ partitioning the cache according to orig
 to [Partitioning the Cache](../configuring-cache#PartitoningCache) According to Origin Server
or Domain.
 Before you can assign cache partitions to specific origin servers and/or
 domains, you must first partition your cache according to size and
-protocol in the [partition.config](partition.config) file.
+protocol in the [volume.config](volume.config) file.
 For step-by-step instructions about partitioning your cache, refer to
 [Partitioning the Cache](../configuring-cache#PartitioningCache). For a description of the
-`partition.config` file, refer to [partition.config](partition.config).
+`volume.config` file, refer to [volume.config](volume.config).
 
 After you modify hosting.config, navigate to the Traffic Server bin
 directory and run the `traffic_line -x` command to apply your changes. When
 you apply the changes to a node in a cluster, Traffic Server automatically
 applies the changes to all other nodes in the cluster.
 
-**IMPORTANT:** The partition configuration must be the same on all nodes in a
+**IMPORTANT:** The volume.configuration must be the same on all nodes in a
 cluster.
 
 
@@ -54,7 +54,7 @@ on a particular partition(for example, `
 `partition_numbers` is a comma-separated list of the partitions on which you
 want to store the content that belongs to the origin server or domain
 listed. The partition numbers must be valid numbers listed in the
-[partition.config](partition.config) file.
+[volume.config](volume.config) file.
 
 **Note:** To allocate more than one partition to an origin server or domain,
 you must enter the partitions in a comma-separated list on one line, as

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/index.en.mdtext?rev=1132938&r1=1132937&r2=1132938&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/index.en.mdtext
(original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/index.en.mdtext
Tue Jun  7 10:05:46 2011
@@ -29,7 +29,7 @@ This section describes Traffic Server co
 * [log_hosts.config](log_hosts.config)
 * [logs_xml.config](logs_xml.config)
 * [parent.config](parent.config)
-* [partition.config](partition.config)
+* [volume.config](volume.config)
 * [records.config](records.config)
 * [remap.config](remap.config)
 * [splitdns.config](splitdns.config)

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/order.txt
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/order.txt?rev=1132938&r1=1132937&r2=1132938&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/order.txt
(original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/order.txt
Tue Jun  7 10:05:46 2011
@@ -7,7 +7,7 @@ ip_allow.config
 log_hosts.config
 logs_xml.config
 parent.config
-partition.config
+volume.config
 records.config
 remap.config
 splitdns.config

Copied: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/volume.config.en.mdtext
(from r1132908, trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/partition.config.en.mdtext)
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/volume.config.en.mdtext?p2=trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/volume.config.en.mdtext&p1=trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/partition.config.en.mdtext&r1=1132908&r2=1132938&rev=1132938&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/partition.config.en.mdtext
(original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/volume.config.en.mdtext
Tue Jun  7 10:05:46 2011
@@ -1,4 +1,4 @@
-Title: Configuration Files - partition.config
+Title: Configuration Files - volume.config
 Notice:    Licensed to the Apache Software Foundation (ASF) under one
            or more contributor license agreements.  See the NOTICE file
            distributed with this work for additional information
@@ -16,55 +16,57 @@ Notice:    Licensed to the Apache Softwa
            specific language governing permissions and limitations
            under the License.
 
-# partition.config # {#parition.config}
+[TOC]
 
-The `partition.config` file enables you to manage your cache space
+# volume.config # {#parition.config}
+
+The `volume.config` file enables you to manage your cache space
 more efficiently and restrict disk usage by creating cache
-partitions of different sizes for specific protocols. You can
-further configure these partitions to store data from certain
+volumes of different sizes for specific protocols. You can
+further configure these volumes to store data from certain
 origin servers and/or domains in
 the [hosting.config](hosting.config) file.
 
-**IMPORTANT:** The partition configuration must be the same on all
+**IMPORTANT:** The volume configuration must be the same on all
 nodes in a cluster. You must stop Traffic Server before you change
-the cache partition size and protocol assignment. For step-by-step
+the cache volume size and protocol assignment. For step-by-step
 instructions about partitioning the cache, refer to
 [Partitioning the Cache](../configuring-cache#PartitioningCache).
 
 
-## Format ## {#Format}
+# Format # {#Format}
 
-For each partition you want to create, enter a line with the
+For each volume you want to create, enter a line with the
 following format:
 
     :::text
-    partition=partition_number  scheme=protocol_type  size=partition_size
+    volume=volume_number  scheme=protocol_type  size=volume_size
 
-where *`partition_number`* is a number between 1 and 255 (the
-maximum number of partitions is 255) and *`protocol_type`* is
-`http`. Traffic Server supports `http` for HTTP partition types;
-*`partition_size`* is the amount of cache space allocated to
-the partition. This value can be either a percentage of the total
+where *`volume_number`* is a number between 1 and 255 (the
+maximum number of volumes is 255) and *`protocol_type`* is
+`http`. Traffic Server supports `http` for HTTP volume types;
+*`volume_size`* is the amount of cache space allocated to
+the volume. This value can be either a percentage of the total
 cache space or an absolute value. The absolute value must be a
 multiple of 128 MB, where 128 MB is the smallest value. If you
 specify a percentage, then the size is rounded down to the closest
 multiple of 128 MB.
 
-Each partition is striped across several disks to achieve parallel
-I/O. For example: if there are four disks, then a 1-GB partition
+Each volume is striped across several disks to achieve parallel
+I/O. For example: if there are four disks, then a 1-GB volume
 will have 256 MB on each disk (assuming each disk has enough free
 space available). If you do not allocate all the disk space in the
 cache, then the extra disk space is not used. You can use the extra
-space later to create new partitions without deleting and clearing
-the existing partitions.
+space later to create new volumes without deleting and clearing
+the existing volumes.
 
 
-## Examples ## {#Examples}
+# Examples # {#Examples}
 
 The following example partitions the cache evenly between HTTP and
 HTTPS requests:
 
     :::text
-    partition=1 scheme=http size=50%
-    partition=2 scheme=https size=50%
+    volume=1 scheme=http size=50%
+    volume=2 scheme=https size=50%
 

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuring-cache/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuring-cache/index.en.mdtext?rev=1132938&r1=1132937&r2=1132938&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuring-cache/index.en.mdtext
(original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuring-cache/index.en.mdtext
Tue Jun  7 10:05:46 2011
@@ -22,19 +22,9 @@ The Traffic Server cache consists of a h
 **object store** that indexes objects according to URLs and their associated 
 headers.
 
-This chapter discusses the following topics: 
+[TOC]
 
-* [The Traffic Server Cache](#TSCache)
-* [The RAM Cache](#RAMCache)
-* [Changing the Size of the RAM Cache](#ChangingSizeRAMCache)
-* [Changing Cache Capacity](#ChangingCacheCapacity)
-* [Partitioning the Cache](#PartitioningCache)
-* [Configuring the Cache Object Size Limit](#ConfiguringCacheObjectSizeLimit)
-* [Clearing the Cache](#ClearingCache)
-* [Removing an Object From the Cache](#RemoveObjectFromCache)
-* [Inspecting the Cache](#InspectingCache)
-
-## The Traffic Server Cache ## {#TSCache}
+# The Traffic Server Cache # {#TSCache}
 
 The Traffic Server cache consists of a high-speed object database called the 
 **object store**. The object store indexes objects according to URLs and associated 
@@ -59,7 +49,7 @@ You can perform the following cache conf
 * Partition the cache by reserving cache disk space for specific protocols and origin servers/domains:
refer to [Partitioning the Cache](#PartitioningCache). 
 * Delete all data in the cache: refer to [Clearing the Cache](#ClearingCache).
 
-## The RAM Cache ## {#RAMCache}
+# The RAM Cache # {#RAMCache}
 
 Traffic Server maintains a small RAM cache of extremely popular objects. This 
 RAM cache serves the most popular objects as quickly as possible and reduces 
@@ -67,7 +57,7 @@ load on disks, especially during tempora
 the RAM cache size to suit your needs, as described in [Changing the Size of 
 the RAM Cache](#ChangingSizeRAMCache) below. 
 
-## Changing the Size of the RAM Cache ## {#ChangingSizeofRAMCache}
+# Changing the Size of the RAM Cache # {#ChangingSizeofRAMCache}
 
 Traffic Server provides a dedicated RAM cache for fast retrieval of popular 
 small objects. The default RAM cache size is automatically calculated based 
@@ -82,8 +72,7 @@ if you increase the size of the RAM cach
 requires more memory for network resources. In such instances, you should return 
 the RAM cache size to its previous value.
 
-##### To change the RAM cache size:  ##### {#changeRAMcachesize}
-
+To change the RAM cache size
 1. Stop Traffic Server. 
 3. Set the variable [_`proxy.config.cache.ram_cache.size`_](../configuration-files/records.config#proxy.config.cache.ram_cache.size)
to specify the size of the RAM cache.
  The default value of -1 means that the RAM cache is automatically sized at approximately
1MB per gigabyte of disk.
@@ -91,102 +80,100 @@ the RAM cache size to its previous value
 
  
 
-## Changing Cache Capacity ## {#ChangingCacheCapacity}
+# Changing Cache Capacity # {#ChangingCacheCapacity}
 
 You can increase or reduce the total amount of disk space allocated to the 
 cache without clearing the content. To check the size of the cache (in bytes), 
 enter the command `traffic_line -r proxy.process.cache.bytes_total`. 
 
-### Increasing Cache Capacity  ### {#IncreasingCacheCapacity}
+## Increasing Cache Capacity  ## {#IncreasingCacheCapacity}
 
 To increase the total amount of disk space allocated to the cache on existing 
 disks or to add new disks to a Traffic Server node, follow the steps below: 
 
 1. Stop Traffic Server. 
 2. Add hardware, if necessary. 
-3. Edit the Traffic Server `storage.config` file: increase the amount of disk space allocated
to the cache on existing disks or describe the new hardware you are adding (refer to [storage.config](../configuration-files/storage.config)).
-4. If you add a new disk, then you must edit the `/etc/rc.d/init.d/traffic_server` file to
add a raw disk binding. Instructions for adding a raw disk binding are located in the Traffic
Server `storage.config` file. 
+3. Edit the Traffic Server [`storage.config`](../configuration-files/storage.config) file:
increase the
+   amount of disk space allocated to the cache on existing disks or describe the new hardware
you are adding.
 5. Restart Traffic Server. 
 
-### Reducing Cache Capacity  ### {#ReducingCacheCapacity}
+## Reducing Cache Capacity  ## {#ReducingCacheCapacity}
 
 To reduce the total amount of disk space allocated to the cache on an existing 
 disk or to remove disks from a Traffic Server node, follow the steps below: 
 
 1. Stop Traffic Server. 
 2. Remove hardware, if necessary. 
-3. Edit the Traffic Server `storage.config` file: reduce the amount of disk space allocated
to the cache on existing disks or delete the reference to the hardware you're removing (refer
to [storage.config](../configuration-files/storage.config)). 
-4. If you remove a disk, then you must edit the `/etc/rc.d/init.d/traffic_server` file to
remove the raw disk binding for the disk. 
+3. Edit the Traffic Server [`storage.config`](../configuration-files/storage.config) file:
reduce the
+  amount of disk space allocated to the cache on existing disks or delete the reference to
the hardware you're removing.
 5. Restart Traffic Server. 
 
 **IMPORTANT:** In the `storage.config` file, a formatted or raw disk must be 
 at least 128 MB. 
 
-## Partitioning the Cache ## {#PartitioningCache}
+# Partitioning the Cache # {#PartitioningCache}
 
 You can manage your cache space more efficiently and restrict disk usage by 
-creating cache partitions with different sizes for specific protocols. You 
-can further configure these partitions to store data from specific origin servers 
-and/or domains. The partition configuration must be the same on all nodes in 
+creating cache volumes with different sizes for specific protocols. You 
+can further configure these volumes to store data from specific origin servers 
+and/or domains. The volume configuration must be the same on all nodes in 
 a cluster. 
 
-### Creating Cache Partitions for Specific Protocols ### {#CreatingCachePartitionsforSpecificProtocols}
+## Creating Cache Partitions for Specific Protocols ## {#CreatingCachePartitionsforSpecificProtocols}
 
-You can create separate partitions for your cache that vary in size to store 
+You can create separate volumes for your cache that vary in size to store 
 content according to protocol. This ensures that a certain amount of disk space 
 is always available for a particular protocol. Traffic Server currently supports 
 the **http** partition type for HTTP objects.
 
-##### To partition the cache according to protocol:  ##### {#partitioncacheaccordingprotocol}
-
-1. In a text editor, open the `partition.config` file located in the Traffic Server `config`
directory. 
-2. Enter a line in the file for each partition you want to create (refer to [partition.config](../configuration-files/partition.config)).

-3. Save and close the `partition.config` file. 
+To partition the cache according to protocol
+1. Enter a line in the [`volume.config`](../configuration-files/volume.config) file for each
volume you want to create
 4. Restart Traffic Server. 
 
-#### Making Changes to Partition Sizes and Protocols  #### {#MakingChangesPartitionSizesProtocols}
+## Making Changes to Partition Sizes and Protocols  ## {#MakingChangesPartitionSizesProtocols}
 
-After you've configured your cache partitions based on protocol, you can make 
+After you've configured your cache volumes based on protocol, you can make 
 changes to the configuration at any time. Before making changes, note the following: 
  
 
-* You must stop Traffic Server before you change the cache partition size and protocol assignment.

-* When you increase the size of a partition, the contents of the partition are _not_ deleted
However, when you reduce the size of a partition, the contents of the partition _are_ deleted.

-* When you change the partition number, the partition is deleted and then recreated, even
if the size and protocol type remain the same. 
-* When you add new disks to your Traffic Server node, partition sizes specified in percentages
will increase proportionately. 
-* A lot of changes to partition sizes might result in disk fragmentation, which affects performance
and hit rate. You should clear the cache before making many changes to cache partition sizes
(refer to [Clearing the Cache](#ClearingCache)).
+* You must stop Traffic Server before you change the cache volume size and protocol assignment.

+* When you increase the size of a volume, the contents of the volume are _not_ deleted. However,
when you reduce the size of a volume, the contents of the volume _are_ deleted. 
+* When you change the volume number, the volume is deleted and then recreated, even if the
size and protocol type remain the same. 
+* When you add new disks to your Traffic Server node, volume sizes specified in percentages
will increase proportionately. 
+* A lot of changes to volume sizes might result in disk fragmentation, which affects performance
and hit rate. You should clear the cache before making many changes to cache volume sizes
(refer to [Clearing the Cache](#ClearingCache)).
 
-### Partitioning the Cache According to Origin Server or Domain ### {#PartitioningCacheAccordingOriginServerDomain}
+## Partitioning the Cache According to Origin Server or Domain ## {#PartitioningCacheAccordingOriginServerDomain}
 
 After you have partitioned the cache according to size and protocol, you can 
-assign the partitions you created to specific origin servers and/or domains. 
-You can assign a partition to a single origin server or to multiple origin 
-servers. However, if a partition is assigned to multiple origin servers, then 
-there is no guarantee on the space available in the partition for each origin 
-server. Content is stored in the partition according to popularity. In addition 
-to assigning partitions to specific origin servers and domains, you must assign 
-a generic partition to store content from all origin servers and domains that 
-are not listed. This generic partition is also used if the partitions for a 
+assign the volumes you created to specific origin servers and/or domains. 
+You can assign a volumes to a single origin server or to multiple origin 
+servers. However, if a volumes is assigned to multiple origin servers, then 
+there is no guarantee on the space available in the volumes for each origin 
+server. Content is stored in the volumes according to popularity. In addition 
+to assigning volumes to specific origin servers and domains, you must assign 
+a generic volume to store content from all origin servers and domains that 
+are not listed. This generic volume is also used if the partitions for a 
 particular origin server or domain become corrupt. If you do not assign a generic 
-partition, then Traffic Server will run in proxy-only mode. 
+volume, then Traffic Server will run in proxy-only mode. 
 
-**Note:** You do _not_ need to stop Traffic Server before you assign partitions 
+**Note:** You do _not_ need to stop Traffic Server before you assign volumes 
 to particular hosts or domains. However, this type of configuration is time-consuming 
 and can cause a spike in memory usage. Therefore, it's best to configure partition 
 assignment during periods of low traffic. 
 
-##### To partition the cache according to hostname and domain:  ##### {#partitioncacheaccordinghostnamedomain}
-
-1. Configure the cache partitions according to size and protocol, as described in [Creating
Cache Partitions for Specific Protocols](#CreatingCachePartitionsSpecificProtocols). 
-2. Create a separate partition based on protocol for each host and domain, as well as an
additional generic partition to use for content that does not belong to these origin servers
or domains. The partitions do not need to be the same size. 
-3. In a text editor, open the `hosting.config` file located in the Traffic Server `config`
directory. 
-4. Enter a line in the file to allocate the partition(s) used for each origin server and/or
domain (refer to [hosting.config](../configuration-files/hosting.config)). 
-5. Assign a generic partition to use for content that does not belong to any of the origin
servers or domains listed in the file. If all partitions for a particular origin server become
corrupt, then Traffic Server will also use the generic partition to store content for that
origin server (see [hosting.config](../configuration-files/hosting.config)). 
-6. Save and close the `hosting.config` file. 
-7. Navigate to the Traffic Server `bin` directory. 
+To partition the cache according to hostname and domain
+1. Configure the cache volumes according to size and protocol, as described in
+   [Creating Cache Partitions for Specific Protocols](#CreatingCachePartitionsSpecificProtocols).

+2. Create a separate volume based on protocol for each host and domain, as well as an additional
+   generic partition to use for content that does not belong to these origin servers or domains.
+   The volumes do not need to be the same size. 
+4. Enter a line in the [`hosting.config`](../configuration-files/hosting.config) file to
allocate the volume(s) used for each origin server and/or domain
+5. Assign a generic volume to use for content that does not belong to any of the origin servers
or domains listed in the file.
+   If all volumes for a particular origin server become corrupt, then Traffic Server will
also use the generic volume to store content
+   for that origin server as per [hosting.config](../configuration-files/hosting.config).

 8. Run the command `traffic_line -x` to apply the configuration changes. 
 
-## Configuring the Cache Object Size Limit ## {#ConfiguringCacheObjectSizeLimit}
+# Configuring the Cache Object Size Limit # {#ConfiguringCacheObjectSizeLimit}
 
 By default, Traffic Server allows objects of any size to be cached. You can 
 change the default behavior and specify a size limit for objects in the cache 
@@ -196,22 +183,22 @@ via the steps below:
    `0` (zero) if you do not want a size limit.
 5. Run the command `traffic_line -x` to apply the configuration changes. 
 
-## Clearing the Cache ## {#ClearingCache}
+# Clearing the Cache # {#ClearingCache}
 
 When you clear the cache, you remove all data from the entire cache - including 
 data in the host database. You should clear the cache before performing certain 
 cache configuration tasks, such as partitioning. You cannot clear the cache 
 when Traffic Server is running. 
 
-##### To clear the cache:  ##### {#clearcache}
-
+To clear the cache
 1. Stop Traffic Server (refer to [Stopping Traffic Server](../getting-started#StoppingTS)).
-2. Enter the following command to clear the cache:  
-`traffic_server -Cclear`  
-The `clear` command deletes all data in the object store and the host database. Traffic Server
does not prompt you to confirm the deletion. 
+2. Enter the following command to clear the cache:
+
+         traffic_server -Cclear
+    The `clear` command deletes all data in the object store and the host database. Traffic
Server does not prompt you to confirm the deletion. 
 3. Restart Traffic Server (refer to [Starting Traffic Server](../getting-started#StoppingTS)).
 
-## Removing an Object From the Cache ## {#RemovinganObjectFromCache}
+# Removing an Object From the Cache # {#RemovinganObjectFromCache}
 
 Traffic Server accepts the custom HTTP request method `PURGE` when removing 
 a specific object from cache. If the object is found in the cache and is successfully 
@@ -222,7 +209,7 @@ In the following example, Traffic Server
 and you want to remove the image `remove_me.jpg` from cache:
 
       $ curl -X PURGE -v "http://example.com/remove_me.jpg"
-	 * About to connect() to example.com port 80 (#0)  
+	 * About to connect() to example.com port 80 (#0)
 	 * Trying 192.0.32.11... connected 
 	 * Connected to example.com (192.0.32.11) port 80 (#0)
 
@@ -243,22 +230,21 @@ Note: The procedure above only removes a
 Server cache. Users may still see the old (removed) content if it was cached 
 by intermediary caches or by the end-users' web browser.
 
-## Inspecting the Cache ## {#InspectingCache}
+# Inspecting the Cache # {#InspectingCache}
 
 Traffic Server provides a Cache Inspector utility that enables you to view, 
 delete, and invalidate URLs in the cache (HTTP only). The Cache Inspector utility 
 is a powerful tool that's capable of deleting _all_ the objects in your cache; 
 therefore, make sure that only authorized administrators are allowed to access 
-this utility. To control which hosts have access via the `mgmt_allow.config` 
-file, see [Controlling Host Access to Traffic Manager](../security-options#ControllingHostAccessTrafficManager).
+this utility, see [Controlling Host Access to Traffic Manager](../security-options#ControllingHostAccessTrafficManager).
  
 
-### Accessing the Cache Inspector Utility  ### {#AccessingCacheInspectorUtility}
+## Accessing the Cache Inspector Utility  ## {#AccessingCacheInspectorUtility}
 
 To access the Cache Inspector utility, follow the steps below:
 
-1. In a text editor, open the `records.config` file located in the Traffic Server `config`
directory. 
-2. Add the following variable at the end of the file: _`CONFIG proxy.config.http_ui_enabled
INT 1`_
+1. In the [`records.config`](../configuration-files/records.config) file add the following
variable:
+2. [_`CONFIG proxy.config.http_ui_enabled INT 1`_](../configuration-files/records.config#proxy.config.http_ui_enabled)
 3. To access the cache inspector in reverse proxy mode, you must add a remap rule to `remap.config`
to expose the URL
    For example: `map http://yourhost.com/myCI http://{cache} @action=allow @src_ip=corp_internal_address`
 4. From the Traffic Server `bin` directory, enter the following command to re-read the configuration
file:
@@ -266,7 +252,7 @@ To access the Cache Inspector utility, f
 5. Open your web browser and configure it to use your Traffic Server as a proxy server. Type
the following URL: `http://yourhost/myCI`
 6. The Cache page opens (see [Using the Cache Page](#UsingCachePage) below).
 
-### Using the Cache Page  ### {#UsingCachePage}
+## Using the Cache Page  ## {#UsingCachePage}
 
 The **Cache page** provides several options that enable you to view and delete 
 the contents of your cache: 

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/hierachical-caching/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/hierachical-caching/index.en.mdtext?rev=1132938&r1=1132937&r2=1132938&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/hierachical-caching/index.en.mdtext
(original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/hierachical-caching/index.en.mdtext
Tue Jun  7 10:05:46 2011
@@ -23,7 +23,7 @@ Traffic Server can participate in cache 
 in one cache are routed to other regional caches, thereby leveraging the contents 
 and proximity of nearby caches. 
 
-[TOC]()
+[TOC]
 
 # Understanding Cache Hierarchies # {#UnderstandingCacheHierarchies}
 



Mime
View raw message