ソースを参照

other minor fixes lurking in my sandbox

svn:r9854
Roger Dingledine 18 年 前
コミット
75754b4d8e
3 ファイル変更3 行追加3 行削除
  1. 1 1
      contrib/exitlist
  2. 1 1
      doc/spec/proposals/111-local-traffic-priority.txt
  3. 1 1
      src/or/dirserv.c

+ 1 - 1
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]

+ 1 - 1
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

+ 1 - 1
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;