From: Nick Mathewson Date: Thu, 29 Jan 2015 19:56:45 +0000 (-0500) Subject: Document unix: addresses X-Git-Tag: tor-0.2.6.3-alpha~100^2~1 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=64bde3ae94f843945bed9f438243de76281bc266;p=thirdparty%2Ftor.git Document unix: addresses --- diff --git a/doc/tor.1.txt b/doc/tor.1.txt index 50ab80ecd9..90dad545c7 100644 --- a/doc/tor.1.txt +++ b/doc/tor.1.txt @@ -273,7 +273,7 @@ GENERAL OPTIONS all sockets will be set to this limit. Must be a value between 2048 and 262144, in 1024 byte increments. Default of 8192 is recommended. -[[ControlPort]] **ControlPort** __PORT__|**auto**:: +[[ControlPort]] **ControlPort** __PORT__|**unix:**__path__|**auto**:: If set, Tor will accept connections on this port and allow those connections to control the Tor process using the Tor Control Protocol (described in control-spec.txt). Note: unless you also specify one or @@ -953,7 +953,7 @@ The following options are useful only for clients (that is, if the same circuit. Currently, two addresses are "too close" if they lie in the same /16 range. (Default: 1) -[[SOCKSPort]] **SOCKSPort** \['address':]__port__|**auto** [_flags_] [_isolation flags_]:: +[[SOCKSPort]] **SOCKSPort** \['address':]__port__|**unix:**__path__|**auto** [_flags_] [_isolation flags_]:: Open this port to listen for connections from SOCKS-speaking applications. Set this to 0 if you don't want to allow application connections via SOCKS. Set it to "auto" to have Tor pick a port for