diff options
| author | Nick Mathewson <nickm@torproject.org> | 2015-01-07 10:39:44 -0500 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2015-01-07 10:39:44 -0500 |
| commit | fb68f507618ab5479471384cc4a1fa8b4bfa99fe (patch) | |
| tree | f737d6c11bc451a2dd63dfd31f2439316c3f8cb7 /src/or/entrynodes.c | |
| parent | da26bb646e4ae6c571dedc29e9b68837e9cb238f (diff) | |
| download | tor-fb68f507618ab5479471384cc4a1fa8b4bfa99fe.tar.gz tor-fb68f507618ab5479471384cc4a1fa8b4bfa99fe.zip | |
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.
Diffstat (limited to 'src/or/entrynodes.c')
| -rw-r--r-- | src/or/entrynodes.c | 4 |
1 files changed, 2 insertions, 2 deletions
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 |