torproject/webwml
1
0
Fork 0
mirror of https://github.com/torproject/webwml.git synced 2025-03-01 14:45:41 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

fix a confusing line in the faq, and also bump up all the accountingmax

Browse Source 
numbers so people don't think 1 gigabyte per day is useful.
This commit is contained in:
Roger Dingledine 2014-06-07 03:43:23 +00:00
parent 6c2bdd0632
commit f97d8cfef5
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/en/faq.wml
View File

@ -2404,7 +2404,7 @@ too.
</p>
<pre>
AccountingStart week 3 10:00
AccountingMax N bytes KB MB GB TB
AccountingMax 500 GBytes
</pre>
<p>
This specifies the maximum amount of data your relay will send during an
@ -2413,12 +2413,12 @@ too.
AccountingStart), then the counters for AccountingMax are reset to 0.
</p>
<p>
Example. Let's say you want to allow 1 GB of traffic every day in each
Example: Let's say you want to allow 50 GB of traffic every day in each
direction and the accounting should reset at noon each day:
</p>
<pre>
AccountingStart day 12:00
AccountingMax 1 GB
AccountingMax 50 GBytes
</pre>
<p>
Note that your relay won't wake up exactly at the beginning of each
@ -2433,9 +2433,10 @@ too.
end up using your entire monthly quota in the first day. Just divide
your monthly amount by 30. You might also consider rate limiting to
spread your usefulness over more of the day: if you want to offer X GB
in each direction, you could set your BandwidthRate to 20*X. For example,
if you have 10 GB to offer each way, you might set your BandwidthRate to
200 KB: this way your relay will always be useful for at least half of
in each direction, you could set your BandwidthRate to 20*X KBytes.
For example,
if you have 50 GB to offer each way, you might set your BandwidthRate to
1000 KBytes: this way your relay will always be useful for at least half of
each day.
</p>