From 21af4b8eb2fe7c1bd4b5486d94d2ab2a309be496 Mon Sep 17 00:00:00 2001 From: Roger Dingledine Date: Sat, 20 Nov 2004 07:35:20 +0000 Subject: [PATCH] better text for AccountingMaxKB document SIGUSR2 svn:r2915 --- trunk/doc/tor.1.in | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/trunk/doc/tor.1.in b/trunk/doc/tor.1.in index e7b94e535e..1504fcbd03 100644 --- a/trunk/doc/tor.1.in +++ b/trunk/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.