Skip to content
Snippets Groups Projects
Commit 688903e9 authored by Roger Dingledine's avatar Roger Dingledine
Browse files

Update "ClientOnly" man page entry

There isn't really any point to messing with it. Resolves ticket 5005.
parent 6d595fa4
No related branches found
No related tags found
No related merge requests found
o Minor bugfixes:
- Update "ClientOnly" man page entry to explain that there isn't
really any point to messing with it. Resolves ticket 5005.
......@@ -499,11 +499,12 @@ The following options are useful only for clients (that is, if
number like 60. (Default: 0)
**ClientOnly** **0**|**1**::
If set to 1, Tor will under no circumstances run as a server or serve
directory requests. The default is to run as a client unless ORPort is
configured. (Usually, 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.) (Default: 0)
If set to 1, Tor will under no circumstances run as a relay or serve
directory requests. This config option is mostly meaningless: we
added it back when we were considering having Tor clients auto-promote
themselves to being relays if they were stable and fast enough. The
current behavior is simply that Tor is a client unless ORPort or
DirPort are configured. (Default: 0)
**ExcludeNodes** __node__,__node__,__...__::
A list of identity fingerprints, nicknames, country codes and address
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment