| Re: [chrony-users] Poor synchronization to local NTP server |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
unruh@xxxxxxxxxxxxxx said:
> The length of the hop is not the most important thing. You could have a
> stable long hop, or an unstable short hop, and the long hop would deliver
> better time.
True, but it could also deliver much worse time if the routing is wildly
asymmetrical.
If you don't know the time, it's hard to figure out if the routing is
symmetric. I've seen some wildly asymmetric but reasonably stable times from
NIST to Silicon Valley.
Maybe we should add geographic coordinates to the NTP protocol so a client can
sanity check the round trip times.
--
These are my opinions. I hate spam.
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.