[ntp:questions] Unreachable Clock Source kept on as sys.peer
hart at ntp.org
Wed May 2 12:18:35 UTC 2012
On Wed, May 2, 2012 at 11:28 AM, <joerg.neulist at gmail.com> wrote:
> during my experimentations I have stumbled upon an unexpected
> behaviour of ntpd (4.2.6p3):
> If ntpd has two sources, one of which is unreachable, while the other
> BECOMES unreachable after being selected as peer, it sometimes
> keeps the second source on as sys.peer (apparently forever, have
> observed it for around twelve hours).
I suspect you're seeing the same issue Miroslav Lichvar reported:
The fix first appeared in 4.2.7p58 and was later backported to 4.2.6p4.
More information about the questions