From: Roger Dingledine Date: Sat, 17 Mar 2007 04:34:31 +0000 (+0000) Subject: other minor fixes lurking in my sandbox X-Git-Tag: tor-0.2.0.1-alpha~332 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=75754b4d8ec92809ecf3eb54b806b6897d890c10;p=thirdparty%2Ftor.git other minor fixes lurking in my sandbox svn:r9854 --- diff --git a/contrib/exitlist b/contrib/exitlist index 86295c7d87..39c32f9ff4 100755 --- a/contrib/exitlist +++ b/contrib/exitlist @@ -218,7 +218,7 @@ def run(): opts, pargs = getopt.getopt(sys.argv[1:], "vx") except getopt.GetoptError, e: print """ -usage: %s [-v] [-x] [host:port [host:port [...]]] +usage: cat ~/.tor/cached-routers* | %s [-v] [-x] [host:port [host:port [...]]] -v verbose output -x invert results """ % sys.argv[0] diff --git a/doc/spec/proposals/111-local-traffic-priority.txt b/doc/spec/proposals/111-local-traffic-priority.txt index fa060b510f..62ee603a25 100644 --- a/doc/spec/proposals/111-local-traffic-priority.txt +++ b/doc/spec/proposals/111-local-traffic-priority.txt @@ -21,7 +21,7 @@ Motivation: they're limited to the same download capacity as upload capacity. And they have to enable rate limiting, or their upstream pipe gets filled up, starts dropping packets, and now their net connection doesn't work - even for non-Tor stuff. So they end up turning off the relaying part. + even for non-Tor stuff. So they end up turning off the relaying part so they can use Tor (and other applications) again. So far this hasn't mattered that much: most of our fast relays are diff --git a/src/or/dirserv.c b/src/or/dirserv.c index 483c6e4c3a..6f11cfd7e8 100644 --- a/src/or/dirserv.c +++ b/src/or/dirserv.c @@ -2093,7 +2093,7 @@ connection_dirserv_stop_blocking_all_on_or_conn(or_connection_t *or_conn) { dir_connection_t *dir_conn, *next; - dir_conn=or_conn->blocked_dir_connections; + dir_conn = or_conn->blocked_dir_connections; while (dir_conn) { next = dir_conn->next_blocked_on_same_or_conn;