Scale CONSENSUS_MIN_SECONDS_BEFORE_CACHING by voting interval
commit6f58481335ac4ce9a1bbeb35218aee3c2274744d
authorNick Mathewson <nickm@torproject.org>
Sat, 31 Jul 2010 17:48:41 +0000 (31 13:48 -0400)
committerNick Mathewson <nickm@torproject.org>
Tue, 17 Aug 2010 15:55:39 +0000 (17 11:55 -0400)
tree75ba2df882a73304c04f9d6c9fecabb198d2e5be
parentb958eae573fd1e2817df628e29d937e2683630ea
Scale CONSENSUS_MIN_SECONDS_BEFORE_CACHING by voting interval

If the voting interval was short enough, the two-minutes delay
of CONSENSUS_MIN_SECONDS_BEFORE_CACHING would confuse bridges
to the point where they would assert before downloading a consensus.
It it was even shorter (<4 minutes, I think), caches would
assert too.  This patch fixes that by having replacing the
two-minutes value with MIN(2 minutes, interval/16).

Bugfix for 1141; the cache bug could occur since 0.2.0.8-alpha, so
I'm calling this a bugfix on that.  Robert Hogan diagnosed this.
Done as a patch against maint-0.2.1, since it makes it hard to
run some kinds of testing networks.
changes/bug1141 [new file with mode: 0644]
src/or/networkstatus.c