summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2004-11-20 07:35:20 +0000
committerRoger Dingledine <arma@torproject.org>2004-11-20 07:35:20 +0000
commit0cec6feb9ef890f1621282499120e9eb0ef6a81c (patch)
tree8f25a57a85164262d73711445ed153c68977c3c8
parentdd19cf6ba3fbde4959c0ae88f4cb5a384b0b077c (diff)
downloadtor-0cec6feb9ef890f1621282499120e9eb0ef6a81c.tar.gz
tor-0cec6feb9ef890f1621282499120e9eb0ef6a81c.zip
better text for AccountingMaxKB
document SIGUSR2 svn:r2915
-rw-r--r--doc/tor.1.in11
1 files changed, 8 insertions, 3 deletions
diff --git a/doc/tor.1.in b/doc/tor.1.in
index e7b94e535e..1504fcbd03 100644
--- a/doc/tor.1.in
+++ b/doc/tor.1.in
@@ -272,9 +272,10 @@ special target string "pass", which prevents subsequent rules from being
considered.
.TP
\fBAccountingMaxKB \fR\fInum\fP
-Never send or receive more than \fInum\fP kilobytes in a given
-accounting period (currently, only months are supported). When the
-number of kilobytes is exhausted, Tor will hibernate until some time
+Never send more than \fInum\fP kilobytes in a given accounting period,
+or receive more than \fInum\fP kilobytes in the period (currently,
+only months are supported). When the number of kilobytes is exhausted,
+Tor will hibernate until some time
in the next accounting period. If you have bandwidth cost issues,
using this option is preferable to setting a low bandwidth, since it
provides users with a collection of fast servers that are up some of
@@ -364,6 +365,10 @@ directory, and kill and restart its helper processes if applicable.
Log statistics about current connections, past connections, and
throughput.
.TP
+\fBSIGUSR2\fR
+Switch all logs to loglevel debug. You can go back to the old loglevels
+by sending a SIGHUP.
+.TP
\fBSIGCHLD\fR
Tor receives this signal when one of its helper processes has exited,
so it can clean up.