Changes between Version 2 and Version 3 of doc/CronBandwidthLimit


Ignore:
Timestamp:
Apr 23, 2010, 4:49:07 AM (10 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/CronBandwidthLimit

    v2 v3  
    2323{{{
    2424#[min] [hour] [day of month] [month] [day of week] [program to be run]
    25 30 8 * * * echo -en "authenticate\r\nsetconf relaybandwidthrate=20000 relaybandwidthburst=20000\r\nquit\r\n" | nc localhost 9051
     2530 8 * * * echo -en "authenticate\r\nsetconf bandwidthrate=20000 bandwidthburst=20000\r\nquit\r\n" | nc localhost 9051
    2626}}}
    2727
    28 This entry will run at the 30th minute of the 8th hour, any day of the month, any month, and any day of the week. Notice that relaybandwidthrate and burst are both in bytes (20kb == 20000 bytes). By using relaybandwidth* instead of bandwidth*, you only limit the speed of relayed traffic on your node. Any traffic that you originate won't be slowed down by the bandwidth limiting.
     28This entry will run at the 30th minute of the 8th hour, any day of the month, any month, and any day of the week. Notice that bandwidthrate and burst are both in bytes (20kb == 20000 bytes).
    2929
    3030We can specify two policies to control deadtime, and time when we need bandwidth for personal uses. The following policies control deadtime at midnight to 8 am using a 300 kb rate and 350 kb burst, and from 8 am till midnight time that we restrict Tor's bandwidth to 20 kb for both.