[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-commits] [tor/master] answer an XXX nickm asked in aa950e6c4
commit 5f182ea10e25ed027cf75627f74013e7c6da2038
Author: Roger Dingledine <arma@xxxxxxxxxxxxxx>
Date: Sun May 29 18:52:37 2011 -0400
answer an XXX nickm asked in aa950e6c4
---
src/or/circuitbuild.c | 2 +-
src/or/main.c | 5 ++++-
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/src/or/circuitbuild.c b/src/or/circuitbuild.c
index 108007e..9509b5a 100644
--- a/src/or/circuitbuild.c
+++ b/src/or/circuitbuild.c
@@ -262,7 +262,7 @@ circuit_build_times_test_frequency(void)
}
/**
- * Retrieve and bounds-check the cbtmintimeout consensus paramter.
+ * Retrieve and bounds-check the cbtmintimeout consensus parameter.
*
* Effect: This is the minimum allowed timeout value in milliseconds.
* The minimum is to prevent rounding to 0 (we only check once
diff --git a/src/or/main.c b/src/or/main.c
index d1ceeec..4fc6437 100644
--- a/src/or/main.c
+++ b/src/or/main.c
@@ -1162,7 +1162,10 @@ run_scheduled_events(time_t now)
* it's not comfortable with the number of available circuits.
*/
/* XXXX022 If our circuit build timeout is much lower than a second, maybe
- we should do this more often? */
+ * we should do this more often? -NM
+ * It can't be lower than 1.5 seconds currently; see
+ * circuit_build_times_min_timeout(). -RD
+ */
circuit_expire_building();
/** 3b. Also look at pending streams and prune the ones that 'began'
_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits