[or-cvs] Update tor-manual-cvs.html

Sun May 15 01:24:53 UTC 2005

Update of /home2/or/cvsroot/website
In directory moria.mit.edu:/tmp/cvs-serv7913

Modified Files:
	tor-manual-cvs.html 
Log Message:
Update tor-manual-cvs.html


Index: tor-manual-cvs.html
===================================================================
RCS file: /home2/or/cvsroot/website/tor-manual-cvs.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -d -r1.6 -r1.7

--- tor-manual-cvs.html	1 May 2005 22:15:57 -0000	1.6
+++ tor-manual-cvs.html	15 May 2005 01:24:46 -0000	1.7
@@ -124,7 +124,7 @@
 &quot;control_auth_cookie&quot;, which Tor will create in its data directory.  This
 authentication methods should only be used on systems with good filesystem
 security.
-<B>DirFetchPeriod </B><I>N</I> <B>seconds</B>|<B>minutes</B>|<B>hours</B>|<B>days</B>|<B>weeks</B>
+<DT><B>DirFetchPeriod </B><I>N</I> <B>seconds</B>|<B>minutes</B>|<B>hours</B>|<B>days</B>|<B>weeks</B><DD>
 Every time the specified period elapses, Tor downloads a directory.
 A directory contains a signed list of all known servers as well as
 their current liveness status. A value of &quot;0 seconds&quot; tells Tor to choose an
@@ -151,9 +151,10 @@
 Where on our circuits should we allow Tor servers that the directory
 servers haven't authenticated as &quot;verified&quot;?  (Default: middle,rendezvous.)
 <DT><B>ClientOnly </B><B>0</B>|<B>1</B><DD>
-If set to 1, Tor will under no circumstances run as a server.  (Usually,
+If set to 1, Tor will under no circumstances run as a server. 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 good server.)
+you are reliable and high-bandwidth enough to be a useful server.)
 <DT><B>EntryNodes </B><I>nickname</I>,<I>nickname</I>,<I>...</I><DD>
 A list of preferred nodes to use for the first hop in the circuit, if possible.
 <DT><B>ExitNodes </B><I>nickname</I>,<I>nickname</I>,<I>...</I><DD>
@@ -200,11 +201,14 @@
 <DT><B>RendExcludeNodes </B><I>nickname</I>,<I>nickname</I>,<I>...</I><DD>
 A list of nodes to never use when choosing a rendezvous point.
 <DT><B>SOCKSPort </B><I>PORT</I><DD>
-Bind to this port to listen for connections from SOCKS-speaking applications.
-Set this to 0 if you don't want to allow application connections. (Default:
-9050)
-<DT><B>SOCKSBindAddress </B><I>IP</I><DD>
-Bind to this address to listen for connections from SOCKS-speaking applications. (Default: 127.0.0.1) You can also specify a port (e.g. 192.168.0.1:9100). This directive can be specified multiple times to bind to multiple addresses/ports.
+Advertise this port to listen for connections from SOCKS-speaking
+applications.  Set this to 0 if you don't want to allow application
+connections. (Default: 9050)
+<DT><B>SOCKSBindAddress </B><I>IP</I>[:<I>PORT</I>]<DD>
+Bind to this address to listen for connections from SOCKS-speaking
+applications. (Default: 127.0.0.1) You can also specify a port
+(e.g. 192.168.0.1:9100). This directive can be specified multiple times
+to bind to multiple addresses/ports.
 <DT><B>SOCKSPolicy </B><I>policy</I>,<I>policy</I>,<I>...</I><DD>
 Set an entrance policy for this server, to limit who can connect to the SOCKS ports. The policies have the same form as exit policies below.
 <DT><B>TrackHostExits </B><I>host</I>,<I>.domain</I>,<I>...</I><DD>
@@ -292,9 +296,11 @@
 <DT><B>NumCPUs </B><I>num</I><DD>
 How many processes to use at once for decrypting onionskins. (Default: 1)
 <DT><B>ORPort </B><I>PORT</I><DD>
-Bind to this port to listen for connections from Tor clients and servers.
-<DT><B>ORBindAddress </B><I>IP</I><DD>
-Bind to this address to listen for connections from Tor clients and servers. (Default: 0.0.0.0)
+Advertise this port to listen for connections from Tor clients and servers.
+<DT><B>ORBindAddress </B><I>IP</I>[:<I>PORT</I>]<DD>
+Bind to this IP address to listen for connections from Tor clients and
+servers. If you specify a port, bind to this port rather than the one
+specified in ORPort. (Default: 0.0.0.0)
 <DT><B>RedirectExit </B><I>pattern target</I><DD>
 Whenever an outgoing connection tries to connect to one of a given set
 of addresses, connect to <I>target</I> (an <I>address:port</I> pair) instead.
@@ -357,9 +363,10 @@
 probably do not want to set this option.  Please coordinate with the other
 admins at <A HREF="mailto:tor-ops at freehaven.net">tor-ops at freehaven.net</A> if you think you should be a directory.
 <DT><B>DirPort </B><I>PORT</I><DD>
-Bind the directory service to this port.
-<DT><B>DirBindAddress </B><I>IP</I><DD>
-Bind the directory service to this address. (Default: 0.0.0.0)
+Advertise the directory service on this port.
+<DT><B>DirBindAddress </B><I>IP</I>[:<I>PORT</I>]<DD>
+Bind the directory service to this address. If you specify a port, bind
+to this port rather than the one specified in DirPort. (Default: 0.0.0.0)
 <DT><B>DirPolicy </B><I>policy</I>,<I>policy</I>,<I>...</I><DD>
 Set an entrance policy for this server, to limit who can connect to the directory ports. The policies have the same form as exit policies above.
 <DT><B>RecommendedVersions </B><I>STRING</I><DD>
@@ -496,6 +503,6 @@
 This document was created by
 <A HREF="../">man2html</A>,
 using the manual pages.<BR>
-Time: 22:12:47 GMT, May 01, 2005
+Time: 01:23:43 GMT, May 15, 2005
 </BODY>
 </HTML>

