From d0d3d77f48102c7b8b565ec941a6b980db7f2422 Mon Sep 17 00:00:00 2001 From: Roger Dingledine Date: Fri, 9 Sep 2005 00:56:26 +0000 Subject: [PATCH] step nine: raise your ulimit -n svn:r4958 --- doc/tor-doc-server.html | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/doc/tor-doc-server.html b/doc/tor-doc-server.html index aa693a488c..6b0169f8e5 100644 --- a/doc/tor-doc-server.html +++ b/doc/tor-doc-server.html @@ -241,14 +241,23 @@ start at boot.

-9. If you control the name servers for your domain, consider setting +9. (Unix only.) Your operating system probably limits the number of open +file descriptors per process to 1024 (or even less). If you plan to be +running a fast exit node, this is probably not enough. You should run +"ulimit -n 8192" (as root) and then su to the user that will run Tor, +or change your defaults (on Debian, add a line like "toruser hard nofile +8192" to your /etc/security/limits.conf file). +

+ +

+10. If you control the name servers for your domain, consider setting your hostname to 'anonymous' or 'proxy' or 'tor-proxy', so when other people see the address in their web logs, they will more quickly understand what's going on.

-10. If your computer isn't running a webserver, please consider +11. If your computer isn't running a webserver, please consider changing your ORPort to 443 and your DirPort to 80. Many Tor users are stuck behind firewalls that only let them browse the web, and this change will let them reach your Tor server. Win32