Author: buildbot
Date: Fri Oct 5 18:43:08 2012
New Revision: 834168
Log:
Staging update by buildbot for tserver
Modified:
websites/staging/trafficserver/trunk/cgi-bin/ (props changed)
websites/staging/trafficserver/trunk/content/ (props changed)
websites/staging/trafficserver/trunk/content/docs/trunk/admin/working-log-files/index.en.html
Propchange: websites/staging/trafficserver/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Oct 5 18:43:08 2012
@@ -1 +1 @@
-1394711
+1394718
Propchange: websites/staging/trafficserver/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Oct 5 18:43:08 2012
@@ -1 +1 @@
-1394711
+1394718
Modified:
websites/staging/trafficserver/trunk/content/docs/trunk/admin/working-log-files/index.en.html
==============================================================================
---
websites/staging/trafficserver/trunk/content/docs/trunk/admin/working-log-files/index.en.html
(original)
+++
websites/staging/trafficserver/trunk/content/docs/trunk/admin/working-log-files/index.en.html
Fri Oct 5 18:43:08 2012
@@ -226,7 +226,7 @@ takes the following actions: </p>
<li>
<p>If the autodelete option is <em>disabled</em> or there are not enough old
log files to delete
for the system to emerge from its low space state, then Traffic Server
issues a warning
- and continues logging until space is exhausted. When avilable space is
consumed, event
+ and continues logging until space is exhausted. When available space is
consumed, event
logging stops. Traffic Server resumes event logging when enough space
becomes available
for it to exit the low space state. To make space available, either
explicitly increase
the logging space limit or remove files from the logging directory manually.
</p>
