summaryrefslogtreecommitdiff
path: root/src/or/circuitbuild.c
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2011-07-11 16:10:24 -0400
committerNick Mathewson <nickm@torproject.org>2011-07-11 16:13:17 -0400
commit2a594fcde94ada2ef38d33d306b7df189a5e495c (patch)
treee195a35db465872a82795d2804f1a687b81b6e22 /src/or/circuitbuild.c
parente253e9577fb7d76bd534b343f0f63559b9a47b4a (diff)
downloadtor-2a594fcde94ada2ef38d33d306b7df189a5e495c.tar.gz
tor-2a594fcde94ada2ef38d33d306b7df189a5e495c.zip
Disable recording new broken conns when we have bootstrapped
Rationale: right now there seems to be no way for our bootstrap status to dip under 100% once it has reached 100%. Thus, recording broken connections after that point is useless, and wastes memory. If at some point in the future we allow our bootstrap level to go backwards, then we should change this rule so that we disable recording broken connection states _as long as_ the bootstrap status is 100%.
Diffstat (limited to 'src/or/circuitbuild.c')
-rw-r--r--src/or/circuitbuild.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/or/circuitbuild.c b/src/or/circuitbuild.c
index 6a411d1945..0e1dd524f6 100644
--- a/src/or/circuitbuild.c
+++ b/src/or/circuitbuild.c
@@ -2117,7 +2117,7 @@ circuit_send_next_onion_skin(origin_circuit_t *circ)
"Looks like client functionality is working.");
control_event_bootstrap(BOOTSTRAP_STATUS_DONE, 0);
control_event_client_status(LOG_NOTICE, "CIRCUIT_ESTABLISHED");
- clear_broken_connection_map();
+ clear_broken_connection_map(1);
if (server_mode(options) && !check_whether_orport_reachable()) {
inform_testing_reachability();
consider_testing_reachability(1, 1);