|
@@ -170,7 +170,7 @@ you don't need to set this; Tor is pretty smart at figuring out whether
|
|
you are reliable and high-bandwidth enough to be a useful server.)
|
|
you are reliable and high-bandwidth enough to be a useful server.)
|
|
|
|
|
|
This option will likely be deprecated in the future; see the NoPublish
|
|
This option will likely be deprecated in the future; see the NoPublish
|
|
-option below.
|
|
|
|
|
|
+option below. (Default: 0)
|
|
.TP
|
|
.TP
|
|
\fBEntryNodes \fR\fInickname\fR,\fInickname\fR,\fI...\fP
|
|
\fBEntryNodes \fR\fInickname\fR,\fInickname\fR,\fI...\fP
|
|
A list of preferred nodes to use for the first hop in the circuit, if possible.
|
|
A list of preferred nodes to use for the first hop in the circuit, if possible.
|
|
@@ -338,6 +338,7 @@ If you set NoPublish 1, Tor will act as a server if you have an ORPort
|
|
defined, but it will not publish its descriptor to the dirservers. This
|
|
defined, but it will not publish its descriptor to the dirservers. This
|
|
option is useful if you're testing out your server, or if you're using
|
|
option is useful if you're testing out your server, or if you're using
|
|
alternate dirservers (e.g. for other Tor networks such as Blossom).
|
|
alternate dirservers (e.g. for other Tor networks such as Blossom).
|
|
|
|
+(Default: 0)
|
|
.TP
|
|
.TP
|
|
\fBNumCPUs \fR\fInum\fP
|
|
\fBNumCPUs \fR\fInum\fP
|
|
How many processes to use at once for decrypting onionskins. (Default: 1)
|
|
How many processes to use at once for decrypting onionskins. (Default: 1)
|