[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[or-cvs] If anybody set DirFetchPostPeriod, give them StatuFetchPeri...
- To: or-cvs@freehaven.net
- Subject: [or-cvs] If anybody set DirFetchPostPeriod, give them StatuFetchPeri...
- From: nickm@seul.org (Nick Mathewson)
- Date: Mon, 29 Nov 2004 21:23:53 -0500 (EST)
- Delivered-to: archiver@seul.org
- Delivered-to: or-cvs-outgoing@seul.org
- Delivered-to: or-cvs@seul.org
- Delivery-date: Mon, 29 Nov 2004 21:24:22 -0500
- Reply-to: or-dev@freehaven.net
- Sender: owner-or-cvs@freehaven.net
Update of /home/or/cvsroot/tor/doc
In directory moria.mit.edu:/tmp/cvs-serv18359/doc
Modified Files:
TODO tor.1.in
Log Message:
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?
Index: TODO
===================================================================
RCS file: /home/or/cvsroot/tor/doc/TODO,v
retrieving revision 1.230
retrieving revision 1.231
diff -u -d -r1.230 -r1.231
--- TODO 29 Nov 2004 23:04:25 -0000 1.230
+++ TODO 30 Nov 2004 02:23:50 -0000 1.231
@@ -15,10 +15,10 @@
o cache and serve running-routers on other nodes?
o cache running-routers
o download running-routers from servers running rc5-cvs or later
-N - pump up periods for fetching things; figure out how to do this
+ o pump up periods for fetching things; figure out how to do this
backward-compatibily, so that people who did set dirfetchpostperiod
get the right behavior.
- - If dirport is set, we should have a maximum dirfetchperiod and
+ o If dirport is set, we should have a maximum dirfetchperiod and
a maximum statusfetchperiod, or else we'll serve very stale stuff.
o Adapt version parsing code to handle new version scheme; document new
version scheme.
Index: tor.1.in
===================================================================
RCS file: /home/or/cvsroot/tor/doc/tor.1.in,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -d -r1.43 -r1.44
--- tor.1.in 28 Nov 2004 15:49:38 -0000 1.43
+++ tor.1.in 30 Nov 2004 02:23:50 -0000 1.44
@@ -67,7 +67,7 @@
.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 @@
\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 @@
\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