summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndrew Lewman <andrew@torproject.org>2007-11-02 02:32:47 +0000
committerAndrew Lewman <andrew@torproject.org>2007-11-02 02:32:47 +0000
commit14be21f31ec032e6cc7ef1d6a0fcd8c2b719bcf2 (patch)
tree36a8c7232d77ba49625ac9ac120ddf9325af68b0
parent832ef9562f43e3f30c05f34a479ce18a685229ae (diff)
downloadtor-14be21f31ec032e6cc7ef1d6a0fcd8c2b719bcf2.tar.gz
tor-14be21f31ec032e6cc7ef1d6a0fcd8c2b719bcf2.zip
Add a comment to the relaybandwidth bug.
svn:r12320
-rw-r--r--doc/TODO3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/TODO b/doc/TODO
index fca2a8a56f..4c2aa93158 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -95,6 +95,9 @@ Things we'd like to do in 0.2.0.x:
also 0.2.0.
- phobos says relaybandwidth* sometimes don't do what we expect.
http://interloper.org/tmp/2007-06-bw-usage.png
+ I believe this is the result of confusion about whether to use
+ relaybandwidth or bandwidthrate to control bandwidth usage for
+ servers. Chances are, this isn't a bug per se. [phobos]
- this notion of authorities notifying servers that they're
unreachable is bunk -- it's leftover from the time when all
servers ran 24/7. now it triggers every time a server goes