diff options
| author | Nick Mathewson <nickm@torproject.org> | 2007-10-30 15:17:07 +0000 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2007-10-30 15:17:07 +0000 |
| commit | c0c2001a5b8fd3907c7ba93eccbd536786f57594 (patch) | |
| tree | c7aa35ecb0eab620cbd592451600347410da4dee /doc/spec/control-spec.txt | |
| parent | 7709fb7143cc272c04f9de3970e4ac0fe3a000d6 (diff) | |
| download | tor-c0c2001a5b8fd3907c7ba93eccbd536786f57594.tar.gz tor-c0c2001a5b8fd3907c7ba93eccbd536786f57594.zip | |
r16279@catbus: nickm | 2007-10-30 11:14:29 -0400
Improved skew reporting: "You are 365 days in the duture" is more useful than "You are 525600 minutes in the future". Also, when we get something that proves we are at least an hour in the past, tell the controller "CLOCK_SKEW MIN_SKEW=-3600" rather than just "CLOCK_SKEW"
svn:r12283
Diffstat (limited to 'doc/spec/control-spec.txt')
| -rw-r--r-- | doc/spec/control-spec.txt | 14 |
1 files changed, 8 insertions, 6 deletions
diff --git a/doc/spec/control-spec.txt b/doc/spec/control-spec.txt index 424deea736..cda883e119 100644 --- a/doc/spec/control-spec.txt +++ b/doc/spec/control-spec.txt @@ -1200,14 +1200,16 @@ $Id$ CLOCK_SKEW SKEW="+" / "-" SECONDS + MIN_SKEW="+" / "-" SECONDS. SOURCE="DIRSERV:IP:Port" / "NETWORKSTATUS:IP:PORT" / "CONSENSUS" If "SKEW" is present, it's an estimate of how far we are from the - time declared in the source. If the source is a DIRSERV, we got - the current time from a connection to a dirserver. If the source is - a NETWORKSTATUS, we decided we're skewed because we got a v2 - networkstatus from far in the future. If the source is - CONSENSUS, we decided we're skewed because we got a networkstatus - consensus from the future. + time declared in the source. (In other words, if we're an hour in + the past, the value is -3600.) "MIN_SKEW" is present, it's a lower + bound. If the source is a DIRSERV, we got the current time from a + connection to a dirserver. If the source is a NETWORKSTATUS, we + decided we're skewed because we got a v2 networkstatus from far in + the future. If the source is CONSENSUS, we decided we're skewed + because we got a networkstatus consensus from the future. {Controllers may want to warn the user if the skew is high, or if multiple skew messages appear at severity WARN. Controllers |