diff options
| author | Mike Perry <mikeperry-git@fscked.org> | 2008-07-04 07:15:51 +0000 |
|---|---|---|
| committer | Mike Perry <mikeperry-git@fscked.org> | 2008-07-04 07:15:51 +0000 |
| commit | f9ecb317b7c97cc2635ac64ff6501dc88374b5d4 (patch) | |
| tree | fff3713961d47de87d30d6f9a0ed2c13e883c148 /contrib/linux-tor-prio.sh | |
| parent | 2365e5ca8cf5a771c3ea52e47c8f16c04a255272 (diff) | |
| download | tor-f9ecb317b7c97cc2635ac64ff6501dc88374b5d4.tar tor-f9ecb317b7c97cc2635ac64ff6501dc88374b5d4.tar.gz | |
Update descriptions of params.
svn:r15648
Diffstat (limited to 'contrib/linux-tor-prio.sh')
| -rw-r--r-- | contrib/linux-tor-prio.sh | 24 |
1 files changed, 13 insertions, 11 deletions
diff --git a/contrib/linux-tor-prio.sh b/contrib/linux-tor-prio.sh index 0ebb47564..473511131 100644 --- a/contrib/linux-tor-prio.sh +++ b/contrib/linux-tor-prio.sh @@ -31,7 +31,7 @@ # to your individual connection. In particular, you should leave *some* # minimum amount of bandwidth for Tor, so that Tor users are not # completely choked out when you use your server's bandwidth. 30% is -# probably a polite choice. +# probably a reasonable choice. More is better of course. # To start the shaping, run it as: # ./linux-tor-prio.sh @@ -61,20 +61,22 @@ TOR_UID=$(id -u tor) # Average ping to most places on the net, milliseconds RTT_LATENCY=40 -# RATE_UP must be less than your connection's upload capacity. If it is -# larger, then the bottleneck will be at your router's queue, which you -# do not control. This will cause congestion and a revert to normal TCP -# fairness no matter what the queing priority is. +# RATE_UP must be less than your connection's upload capacity in +# kbits/sec. If it is larger, then the bottleneck will be at your +# router's queue, which you do not control. This will cause congestion +# and a revert to normal TCP fairness no matter what the queing +# priority is. RATE_UP=5000 -# RATE_UP_TOR is the minimum speed your Tor connections will have. -# They will have at least this much bandwidth for upload. In general, -# you probably shouldn't set this too low, or else Tor users who use -# your node will be completely choked out whenever your machine -# does any other network activity. That is not very fun. +# RATE_UP_TOR is the minimum speed your Tor connections will have in +# kbits/sec. They will have at least this much bandwidth for upload. +# In general, you probably shouldn't set this too low, or else Tor +# users who use your node will be completely choked out whenever your +# machine does any other network activity. That is not very fun. RATE_UP_TOR=1500 -# RATE_UP_TOR_CEIL is the maximum rate allowed for all Tor trafic +# RATE_UP_TOR_CEIL is the maximum rate allowed for all Tor trafic in +# kbits/sec. RATE_UP_TOR_CEIL=5000 CHAIN=OUTPUT |