summaryrefslogtreecommitdiff
path: root/doc/tor.1.in
diff options
context:
space:
mode:
authorPeter Palfrader <peter@palfrader.org>2006-01-12 02:10:25 +0000
committerPeter Palfrader <peter@palfrader.org>2006-01-12 02:10:25 +0000
commitfdbd0791e239dc676be2dbdc71e56af2ff464b69 (patch)
tree428036670e01900b75889e24837e7043f1f80ce9 /doc/tor.1.in
parent20bcce490a77d930228fd36053c2cb9400f348e5 (diff)
downloadtor-fdbd0791e239dc676be2dbdc71e56af2ff464b69.tar.gz
tor-fdbd0791e239dc676be2dbdc71e56af2ff464b69.zip
Fix bold vs. italics in the FILES sections, update date
svn:r5821
Diffstat (limited to 'doc/tor.1.in')
-rw-r--r--doc/tor.1.in22
1 files changed, 12 insertions, 10 deletions
diff --git a/doc/tor.1.in b/doc/tor.1.in
index e3f408e879..e0b5d097b2 100644
--- a/doc/tor.1.in
+++ b/doc/tor.1.in
@@ -1,4 +1,4 @@
-.TH TOR 1 "September 2005" "TOR"
+.TH TOR 1 "January 2006" "TOR"
.SH NAME
tor \- The second-generation onion router
.SH SYNOPSIS
@@ -694,22 +694,24 @@ If this signal exists on your platform, Tor catches and ignores it.
.SH FILES
.LP
.TP
-.I @CONFDIR@/\fBtorrc\fP
+.B @CONFDIR@/torrc
The configuration file, which contains "option value" pairs.
.LP
.TP
-.I @LOCALSTATEDIR@/\fBlib/tor/\fP
+.B @LOCALSTATEDIR@/lib/tor/
The tor process stores keys and other data here.
.LP
.TP
-\fIDataDirectory\fP/\fBapproved-routers\fP This file lists nickname
-to identity bindings for NamingAuthoritativeDirectory. Each line
-lists a nickname and a fingerprint seperated by whitespace. See your
+.B \fIDataDirectory\fP/approved-routers
+Only for naming authoritative directory servers
+(see \fBNamingAuthoritativeDirectory\fP).
+This file lists nickname to identity bindings. Each line lists a
+nickname and a fingerprint seperated by whitespace. See your
\fBfingerprint\fP file in the \fIDataDirectory\fP for an example line.
-If the nickname is \fB!reject\fP then descriptors from the given identity
-(fingerprint) are rejected by the authoritative directory server. If
-it is \fB!invalid\fP then descriptors are accepted but marked in the
-directory as not valid (not recommended).
+If the nickname is \fB!reject\fP then descriptors from the given
+identity (fingerprint) are rejected by the authoritative directory
+server. If it is \fB!invalid\fP then descriptors are accepted but marked
+in the directory as not valid, that is not recommended.
.SH SEE ALSO
.BR privoxy (1),
.BR tsocks (1),