mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-09-21 13:34:59 +02:00
105b94b75b
Right now, Tor routers don't save the maxima values from the bw_history_t between sessions. That's no good, since we use those values to determine bandwidth. This code adds a new BWHist.*Maximum set of values to the state file. If they're not present, we estimate them by taking the observed total bandwidth and dividing it by the period length, which provides a lower bound. This should fix bug 1863. I'm calling it a feature.
17 lines
774 B
Plaintext
17 lines
774 B
Plaintext
o Minor features
|
|
- Servers now save observed maximum bandwidth throughput rates
|
|
to their state file (along with total usage, which was already
|
|
saved) so that they can determine their correct estimated
|
|
bandwidth on restart. Resolves bug 1863, where Tor servers
|
|
would reset their estimated bandwidth to 0 after restarting.
|
|
|
|
o Minor bugfixes
|
|
- Fix a bug in banwidth history state parsing that could have been
|
|
triggered if a future version of Tor ever changed the timing
|
|
granularity at which bandwidth history is measured. Bugfix on
|
|
Tor 0.1.1.11-alpha.
|
|
- Correctly clear out dir_read/dir_write history when there is an
|
|
error parsing any bw history value from the state file. Bugfix on
|
|
Tor 0.2.2.15-alpha.
|
|
|