summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2005-05-01 19:36:56 +0000
committerRoger Dingledine <arma@torproject.org>2005-05-01 19:36:56 +0000
commit383063f2b53a8bd5aa35d8003b9f7bf16fb0b65e (patch)
tree634c9d388db28e0c002fdeaeefd841c0cf9f0a28
parent729e7200955d0b361ca084a2d7cad56e1bca4b53 (diff)
downloadtor-383063f2b53a8bd5aa35d8003b9f7bf16fb0b65e.tar.gz
tor-383063f2b53a8bd5aa35d8003b9f7bf16fb0b65e.zip
clarify accountingmax in man page
svn:r4151
-rw-r--r--doc/tor.1.in3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/tor.1.in b/doc/tor.1.in
index 8cb99bf075..d12c887923 100644
--- a/doc/tor.1.in
+++ b/doc/tor.1.in
@@ -342,6 +342,9 @@ uploaded whenever it changes. (Default: 20 minutes.)
\fBAccountingMax \fR\fIN\fR \fBbytes\fR|\fBKB\fR|\fBMB\fR|\fBGB\fR|\fBTB\fP
Never send more than the specified number of bytes in a given
accounting 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
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