From e764d00e15bc3059bb7f204bb39b0ff9c4c45118 Mon Sep 17 00:00:00 2001 From: Nick Mathewson Date: Tue, 30 Nov 2004 02:23:51 +0000 Subject: If anybody set DirFetchPostPeriod, give them StatuFetchPeriod instead. Impose minima and maxima for all *Period options; impose even tighter maxima for fetching if we are a caching dirserver. Clip rather than rejecting. arma: are these good? svn:r3024 --- doc/tor.1.in | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc/tor.1.in') diff --git a/doc/tor.1.in b/doc/tor.1.in index 05bf835a53..c944b8e155 100644 --- a/doc/tor.1.in +++ b/doc/tor.1.in @@ -67,7 +67,7 @@ rather than connecting directly to any directory servers. .TP \fBKeepalivePeriod \fR\fINUM\fP To keep firewalls from expiring connections, send a padding keepalive -cell on open connections every NUM seconds. (Default: 300) +cell on open connections every NUM seconds. (Default: 5 minutes.) .TP \fBMaxConn \fR\fINUM\fP Maximum number of simultaneous sockets allowed. You probably don't need @@ -119,7 +119,7 @@ information about the current state of known servers. (Default: 20 minutes.) \fBRendPostPeriod \fR\fIN\fR \fBseconds\fR|\fBminutes\fR|\fBhours\fR|\fBdays\fR|\fBweeks\fP Every time the specified period elapses, Tor uploads any rendezvous service descriptors to the directory servers. This information is also -uploaded whenever it changes. (Default: 10 minutes.) +uploaded whenever it changes. (Default: 20 minutes.) .SH CLIENT OPTIONS .PP @@ -282,7 +282,7 @@ considered. \fBDirPostPeriod \fR\fIN\fR \fBseconds\fR|\fBminutes\fR|\fBhours\fR|\fBdays\fR|\fBweeks\fP Every time the specified period elapses, Tor uploads its server descriptors to the directory servers. This information is also -uploaded whenever it changes. (Default: 10 minutes.) +uploaded whenever it changes. (Default: 20 minutes.) .TP \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 -- cgit v1.2.3-54-g00ecf