[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[or-cvs] better text for AccountingMaxKB
Update of /home2/or/cvsroot/tor/doc
In directory moria.mit.edu:/home2/arma/work/onion/cvs/tor/doc
Modified Files:
tor.1.in
Log Message:
better text for AccountingMaxKB
document SIGUSR2
Index: tor.1.in
===================================================================
RCS file: /home2/or/cvsroot/tor/doc/tor.1.in,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -d -r1.38 -r1.39
--- tor.1.in 16 Nov 2004 02:19:55 -0000 1.38
+++ tor.1.in 20 Nov 2004 07:35:20 -0000 1.39
@@ -272,9 +272,10 @@
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 @@
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.