From: Roger Dingledine <arma@torproject.org>
Date: Wed, 10 Nov 2004 00:19:04 +0000 (+0000)
Subject: DirFetchPostPeriod is not a sub-element of AllowUnverifiedNodes
X-Git-Tag: debian-version-0.0.8+0.0.9pre5-1~17
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=d150d458a7267ec8e2eab2de152cf71a36565eb3;p=thirdparty%2Ftor.git

DirFetchPostPeriod is not a sub-element of AllowUnverifiedNodes


svn:r2764
---

diff --git a/doc/tor.1.in b/doc/tor.1.in
index 8617f0c0fd..94fbf7a90d 100644
--- a/doc/tor.1.in
+++ b/doc/tor.1.in
@@ -90,7 +90,8 @@ The following options are useful only for clients (that is, if \fBSOCKSPort\fP i
 \fBAllowUnverifiedNodes\fR \fBentry\fR|\fBexit\fR|\fBmiddle\fR|\fBintroduction\fR|\fBrendezvous\fR|...\fP
 Where on our circuits should we allow Tor servers that the directory
 servers haven't authenticated as "verified"?  (Default: middle,rendezvous.)
-\fBdirfetchpostperiod \fR\fIseconds\fP
+.TP
+\fBDirFetchPostPeriod \fR\fIseconds\fP
 Every N seconds, Tor downloads a fresh directory, and re-uploads
 information about hidden services to the directory servers.  If
 running as a server, Tor also re-uploads information about itself to