answer an XXX nickm asked in aa950e6c4

diff --git a/src/or/circuitbuild.c b/src/or/circuitbuild.c
index 108007e3841a28ddbb1cb4ff657d32e3aeaef8fd..9509b5ad18e60564d8a6b5a7f7a6fa0b31498eec 100644 (file)
--- 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 d1ceeec3479826bb0183c3183fb0519c625c2f3c..4fc643706ca7c7adbb37f64f08ad116701ebf4c2 100644 (file)
--- 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'