clean up tor-doc-server instructions, and get rid of step four entirely.
Roger Dingledine

Roger Dingledine commited on 2007-10-01 08:53:29
Zeige 1 geänderte Dateien mit 14 Einfügungen und 67 Löschungen.

... ...
@@ -125,13 +125,9 @@ so your server can reach the other Tor servers.
125 125
 </p>
126 126
 
127 127
 <p>
128
-5. Start your server: if you installed from source you can just
129
-run <tt>tor</tt>, whereas packages typically launch Tor from their
130
-initscripts or startup scripts. If it logs any
131
-warnings, address them. (By default Tor logs to stdout,
132
-but some packages log to <tt>/var/log/tor/</tt> or <a
133
-href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#Logs">other
134
-locations</a>. You can edit your torrc to configure log locations.)
128
+5. Restart your server. If it <a
129
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#Logs">logs
130
+any warnings</a>, address them.
135 131
 </p>
136 132
 
137 133
 <p>
... ...
@@ -146,9 +142,9 @@ where new development releases are announced.
146 142
 <p>
147 143
 7. Have a look at the manual.
148 144
 The <a href="<page tor-manual>">manual</a> for the
149
-latest stable version provides detailed instructions for how to install
150
-and use Tor, including configuration of client and server options.
151
-If you are running the development version of Tor the manual is available
145
+latest stable version provides a list of all the possible configuration
146
+options for both clients and servers.
147
+If you are running the development version of Tor, the manual is available
152 148
 <a href="<page tor-manual-dev>">here</a>.
153 149
 </p>
154 150
 
... ...
@@ -194,7 +190,7 @@ to get ideas how you can increase the security of your server.
194 190
 
195 191
 <p>
196 192
 9. Decide what exit policy you want. By default your server allows
197
-access to many popular services, but we restrict some (such as port 25)
193
+access to many popular services, but restricts some (such as port 25)
198 194
 due to abuse potential. You might want an exit policy that is
199 195
 less restrictive or more restrictive; edit your torrc appropriately.
200 196
 Read the FAQ entry on <a
... ...
@@ -289,62 +285,13 @@ you may find the initscripts in contrib/tor.sh or contrib/torctl useful.
289 285
 </p>
290 286
 
291 287
 <p>
292
-When you change your Tor configuration, <a
293
-href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#Restarting">in
294
-most cases you can reload your configuration without restarting Tor</a>,
295
-and remember to verify that your server still works correctly after
296
-the change.
297
-</p>
298
-
299
-<hr />
300
-
301
-<a id="register"></a>
302
-<a id="email"></a>
303
-<!-- <h2><a class="anchor" href="#register">Step Four: Register your nickname</a></h2> -->
304
-<h2><a class="anchor" href="#email">Step Four: Let us know about your server</a></h2>
305
-<br />
306
-
307
-<p>
308
-Let it run a few weeks to make sure it's actually working and that you're
309
-happy with its level of resource use. Then if you want, send us email
310
-with contact info and details. <!--register your server. -->
311
-This <!-- reserves your nickname so nobody else can take it, and --> lets us
312
-contact you if you need to upgrade or something goes wrong.
313
-</p>
314
-
315
-<p>
316
-Send mail to <a
317
-href="mailto:tor-ops@freehaven.net">tor-ops@freehaven.net</a> with a
318
-subject of '[New Server] &lt;your server's nickname&gt;' and
319
-include the following information in the message:
320
-</p>
321
-<ul>
322
-<li>Your server's nickname</li>
323
-<li>The fingerprint for your server's identity key. This is <a
324
-href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#Logs">logged</a>
325
-at startup:
326
-something like "<tt>moria1 FFCB 46DB 1339 DA84 674C 70D7 CB58 6434
327
-C437 0441</tt>".
328
-<!--
329
-It is also written to the "fingerprint" file in your DataDirectory.
330
-&mdash; on Windows, look in
331
-\<i>username</i>\Application&nbsp;Data\tor\ or \Application&nbsp;Data\tor\;
332
-on OS X, look in /Library/Tor/var/lib/tor/; and on Linux/BSD/Unix,
333
-look in /var/lib/tor or ~/.tor)
334
--->
335
-</li>
336
-<li>Who you are, so we know whom to contact if a problem arises</li>
337
-<li>What kind of connectivity the new server will have</li>
338
-</ul>
339
-
340
-<p>
341
-Due to the number of emails we get, we may not be able to respond to
342
-every mail. But please be assured that we're very happy you're helping
343
-to make the Tor network grow! If you have problems making it run
344
-smoothly, let us know and we'll try to help.
345
-<!--Then we'll evaluate your server for another week or two to make
346
-sure it stays up and works; so don't be surprised if it takes a
347
-while for us to reply. -->
288
+When you change your Tor configuration, remember to verify that your
289
+server still works correctly after the change. Be sure to set your
290
+"ContactInfo" line in the torrc so we can contact you if you need to
291
+upgrade or something goes wrong. If you have problems or questions, see
292
+the <a href="<page documentation>#Support">Support</a> section or
293
+<a href="<page contact>">contact us</a> on the tor-ops list. Thanks
294
+for helping to make the Tor network grow!
348 295
 </p>
349 296
 
350 297
 <hr />
351 298