summaryrefslogtreecommitdiff
path: root/doc/TUNING
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2020-08-14 09:21:02 -0400
committerNick Mathewson <nickm@torproject.org>2020-08-14 09:21:28 -0400
commit563f8610fd7471bd564b0f2e81223d7eb2e64da0 (patch)
treecd0837f76090286c0ce95569b12cc7ac1fd840a2 /doc/TUNING
parent8669ace2fb4159b8782d181894a5e53125444ed4 (diff)
downloadtor-563f8610fd7471bd564b0f2e81223d7eb2e64da0.tar.gz
tor-563f8610fd7471bd564b0f2e81223d7eb2e64da0.zip
Revise trac.torproject.org urls to refer to gitlab replacements.
Closes #40101.
Diffstat (limited to 'doc/TUNING')
-rw-r--r--doc/TUNING15
1 files changed, 7 insertions, 8 deletions
diff --git a/doc/TUNING b/doc/TUNING
index 24552a38cb..7da37e1adc 100644
--- a/doc/TUNING
+++ b/doc/TUNING
@@ -1,13 +1,13 @@
-Most operating systems limit an amount of TCP sockets that can be used
+Most operating systems limit an amount of TCP sockets that can be used
simultaneously. It is possible for a busy Tor relay to run into these
-limits, thus being unable to fully utilize the bandwidth resources it
+limits, thus being unable to fully utilize the bandwidth resources it
has at its disposal. Following system-specific tips might be helpful
to alleviate the aforementioned problem.
Linux
-----
-Use 'ulimit -n' to raise an allowed number of file descriptors to be
+Use 'ulimit -n' to raise an allowed number of file descriptors to be
opened on your host at the same time.
FreeBSD
@@ -17,7 +17,7 @@ Tune the followind sysctl(8) variables:
* kern.maxfiles - maximum allowed file descriptors (for entire system)
* kern.maxfilesperproc - maximum file descriptors one process is allowed
to use
- * kern.ipc.maxsockets - overall maximum numbers of sockets for entire
+ * kern.ipc.maxsockets - overall maximum numbers of sockets for entire
system
* kern.ipc.somaxconn - size of listen queue for incoming TCP connections
for entire system
@@ -31,8 +31,8 @@ Mac OS X
Since Mac OS X is BSD-based system, most of the above hold for OS X as well.
However, launchd(8) is known to modify kern.maxfiles and kern.maxfilesperproc
-when it launches tor service (see launchd.plist(5) manpage). Also,
-kern.ipc.maxsockets is determined dynamically by the system and thus is
+when it launches tor service (see launchd.plist(5) manpage). Also,
+kern.ipc.maxsockets is determined dynamically by the system and thus is
read-only on OS X.
OpenBSD
@@ -79,8 +79,7 @@ Disclaimer
Do note that this document is a draft and above information may be
technically incorrect and/or incomplete. If so, please open a ticket
-on https://trac.torproject.org or post to tor-relays mailing list.
+on https://gitlab.torproject.org or post to tor-relays mailing list.
Are you running a busy Tor relay? Let us know how you are solving
the out-of-sockets problem on your system.
-