[or-cvs] r9032: Updated the FILES section with info from http://archives.seu (tor/trunk/doc)
phobos at seul.org
phobos at seul.org
Thu Dec 7 05:10:01 UTC 2006
Date: 2006-12-07 00:09:54 -0500 (Thu, 07 Dec 2006)
New Revision: 9032
Updated the FILES section with info from
--- tor/trunk/doc/tor.1.in 2006-12-06 12:48:13 UTC (rev 9031)
+++ tor/trunk/doc/tor.1.in 2006-12-07 05:09:54 UTC (rev 9032)
@@ -903,16 +903,49 @@
The tor process stores keys and other data here.
+The most recently downloaded network status document for each authority. Each file holds one such document; the filenames are the hexadecimal identity key fingerprints of the directory authorities.
+These files hold downloaded router statuses. Some routers may appear more than once; if so, the most recently published descriptor is used. The ".new" file is an append-only journal; when it gets too large, all entries are merged into a new cached-routers file.
+A set of persistent key-value mappings. These are documented in the file. These include:
+.IP "- The current entry guards and their status."
+.IP "- The current bandwidth accounting values (unused so far; see below)."
+.IP "- When the file was last written"
+.IP "- What version of Tor generated the state file"
+.IP "- A short history of bandwidth usage, as produced in the router descriptors."
+Used to track bandwidth accounting values (when the current period starts and ends; how much has been read and written so far this period). Soon to be obsoleted by state. Only used when bandwidth accounting is enabled.
+Used for cookie authentication with the controller. Regenerated on startup. See control-spec.txt for details. Only used when cookie authentication is enabled.
+Only used by servers. Holds identity keys and onion keys.
+Only used by servers. Holds the fingerprint of the server's identity key.
+Only used by servers. Holds the most recently generate router descriptor.
-Only for naming authoritative directory servers
-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, that is, not recommended.
+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, that is, not recommended.
.SH SEE ALSO
.BR privoxy (1),
.BR tsocks (1),
More information about the tor-commits