RelayBandWidthRate and Burst control how much bandwidth the tor daemon is allowed to use (average and burst obviously), AccountingMax is how much bandwidth the daemon is allowed to use over a given period, and AccountingStart definite that period (in my config a period is a month, and it start at midnight of the first day).
Also, once you start it, give it an hour or so to appear in the tor swarm. As long as you have "Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor." in your logs, you should be fine and only have to wait.
First, as a latin american activist, thank you for supporting Tor!!
Please consider the following... It's better for the Tor network to don't have a limit on the bandwidth and let the relay just hibernate when it reachs the 500 GB. If you are able to do this, please give it a try.
Tor has some sane defaults, so you don't need to edit much. I've started running a relay (no exit) node for the challenge, and this is what I'm using:
RelayBandWidthRate and Burst control how much bandwidth the tor daemon is allowed to use (average and burst obviously), AccountingMax is how much bandwidth the daemon is allowed to use over a given period, and AccountingStart definite that period (in my config a period is a month, and it start at midnight of the first day).Also, once you start it, give it an hour or so to appear in the tor swarm. As long as you have "Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor." in your logs, you should be fine and only have to wait.