From fb68f507618ab5479471384cc4a1fa8b4bfa99fe Mon Sep 17 00:00:00 2001 From: Nick Mathewson Date: Wed, 7 Jan 2015 10:39:44 -0500 Subject: 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. --- src/or/entrynodes.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/or/entrynodes.c') 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 -- cgit v1.2.3-54-g00ecf