From: Nick Mathewson Date: Wed, 7 Jan 2015 15:39:44 +0000 (-0500) Subject: Lower the delay before saving guard status to disk X-Git-Tag: tor-0.2.6.3-alpha~140^2 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=fb68f507618ab5479471384cc4a1fa8b4bfa99fe;p=thirdparty%2Ftor.git Lower the delay before saving guard status to disk "Maybe this time should be reduced, since we are considering guard-related changes as quite important? It would be a pity to settle on a guard node, then close the Tor client fast and lose that information." Closes 12485. --- diff --git a/changes/bug12485 b/changes/bug12485 new file mode 100644 index 0000000000..53ce33ef7b --- /dev/null +++ b/changes/bug12485 @@ -0,0 +1,4 @@ + o Minor features (Guard nodes): + - Reduce the time delay before saving guard status to disk from 10 + minute to 30 seconds (or from one hour to 10 minutes if + AvoidDiskWrites is set). Closes ticket 12485. diff --git a/src/or/entrynodes.c b/src/or/entrynodes.c index 05ed56072d..116f047074 100644 --- a/src/or/entrynodes.c +++ b/src/or/entrynodes.c @@ -1525,10 +1525,10 @@ entry_guards_parse_state(or_state_t *state, int set, char **msg) /** How long will we let a change in our guard nodes stay un-saved * when we are trying to avoid disk writes? */ -#define SLOW_GUARD_STATE_FLUSH_TIME 3600 +#define SLOW_GUARD_STATE_FLUSH_TIME 600 /** How long will we let a change in our guard nodes stay un-saved * when we are not trying to avoid disk writes? */ -#define FAST_GUARD_STATE_FLUSH_TIME 600 +#define FAST_GUARD_STATE_FLUSH_TIME 30 /** Our list of entry guards has changed, or some element of one * of our entry guards has changed. Write the changes to disk within