summaryrefslogtreecommitdiff
path: root/doc/tor.1.txt
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2011-01-26 11:45:37 -0500
committerNick Mathewson <nickm@torproject.org>2011-01-26 11:45:37 -0500
commit1dd98891d74cbd7e4e64b0943254dc4a78fb658e (patch)
treed10af916456e1f80dfc170d2c5be0cd58f2c02ef /doc/tor.1.txt
parent5ce8182bdb45c41d8c5f9fea173c2ade1a18bfbb (diff)
downloadtor-1dd98891d74cbd7e4e64b0943254dc4a78fb658e.tar.gz
tor-1dd98891d74cbd7e4e64b0943254dc4a78fb658e.zip
Explain soft shutdown mode a little better in the accountingmax documentation
Diffstat (limited to 'doc/tor.1.txt')
-rw-r--r--doc/tor.1.txt4
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/tor.1.txt b/doc/tor.1.txt
index c8608eb845..8fe73b026b 100644
--- a/doc/tor.1.txt
+++ b/doc/tor.1.txt
@@ -900,7 +900,9 @@ is non-zero):
period, or receive more than that number in the period. For example, with
AccountingMax set to 1 GB, a server could send 900 MB and receive 800 MB
and continue running. It will only hibernate once one of the two reaches 1
- GB. When the number of bytes is exhausted, Tor will hibernate until some
+ GB. When the number of bytes gets low, Tor will stop accepting new
+ connections and circuits. When the number of bytes
+ is exhausted, Tor will hibernate until some
time in the next accounting period. To prevent all servers from waking at
the same time, Tor will also wait until a random point in each period
before waking up. If you have bandwidth cost issues, enabling hibernation