Add installation instructions, tidy some links and wording.

Author: Ben Cotton

README.md

@@ -6,13 +6,19 @@ It supports expiring, local file caching to reduce the number of calls triggered
 
 Support for multiple URLs provides a simple mechanism to ensure high-availability for configuration information. The cache_config tool will attempt to pull configuration from each URL, stopping after the first successful pull happens.
 
+## Installation
+
+On Windows, put the cache_config.exe file in the HTCondor bin directory.
+
+On other OSes, put the cache_config.py file in the HTCondor bin directory.
+
 ## Options
 
 	cache_config.[exe|py] CacheFile CacheTTL LockTTL URL1 [URL2 ...]
 
-* CacheFile - The file name for the cached config on local disk
-* CacheTTL - The time-to-live for the cache file
-* LockTTL - The time-to-live for the file lock
+* CacheFile - The file name for the cached config on local disk (in seconds)
+* CacheTTL - The time-to-live for the cache file (in seconds)
+* LockTTL - The time-to-live for the file lock (in seconds)
 * URL1 - The first URL to check
 * URL2, URL3, ... - Additional, optional failover URLs to check
 
@@ -23,6 +29,9 @@ cache_config checks for an existing, local, cache file to determine whether the
 acquired, with its own TTL to avoid deadlock cases. cache_config then gets the configuration file by attempting to read from the list of URLs for the configuration data. If any error occurs in reading from the first URL, the second is attempted, then the third, and so on, until configuration is successfully fetched and cached. Should all URLs fail, cache_config returns the existing, stale, configuration with additional configuration settings embedded in the output that publish the details of the failures.
 
 
+## Installation
+
+
 ## HTCondor Configuration
 
 In using cache_config with HTCondor it is recommended you copy it to your condor\bin directory (the BIN directory in your current HTCondor configuration). When configuring HTCondor, it is recommended you have a local configuration file that will get HTCondor up and running, then use the following line within that file to fetch the detailed configuration for the machine:
@@ -31,7 +40,7 @@ In using cache_config with HTCondor it is recommended you copy it to your condor
 
 The above line should appear last in your local configuration file to ensure that any configuration sent to HTCondor via the fetch URL overrides any of the local bootstrap configuration.
 
-Note: If using CacheConfig for Windows replace `$(BIN)\cache_config.py` with `$(BIN)\cache_config.exe` in the configuration line above.
+Note: If using cache_config for Windows replace `$(BIN)\cache_config.py` with `$(BIN)\cache_config.exe` in the configuration line above.
 
 
 ## Using `cache_config` with CycleServer
@@ -46,11 +55,11 @@ To fetch your configuration from a CycleServer instance, make your configuration
 ## See Also
 
 * [HTCondor][htcondor] - high throughput computing from the University of Wisconsin
-* For more information on "Configuration with Pipes" in HTCondor, please see the HTCondor manual. In the 7.6 manual the appropriate section is [3.3.1.4][configwithpipes]
+* For more information on "Configuration with Pipes" in HTCondor, please see the HTCondor manual. In the 8.0 manual the appropriate section is [3.3.1.4][configwithpipes]
 
 ## Copyright
 
-Copyright (C) 2007-2012, Cycle Computing, LLC.
+Copyright (C) 2007-2013, Cycle Computing, LLC.
 
 ## License
 
@@ -63,4 +72,4 @@ Unless required by applicable law or agreed to in writing, software distributed
 [cycleserver]:http://www.cyclecomputing.com/cycleserver/overview
 [htcondor]:http://research.cs.wisc.edu/htcondor
 [curl]:http://curl.haxx.se/
-[configwithpipes]:http://research.cs.wisc.edu/htcondor/manual/v7.8/3_3Configuration.html#SECTION00431400000000000000
+[configwithpipes]:http://research.cs.wisc.edu/htcondor/manual/v8.0/3_3Configuration.html#SECTION00431400000000000000