[ntp:questions] Unreachable Clock Source kept on as sys.peer

2012-05-02 Thread joerg . neulist
Hello everyone, 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

Re: [ntp:questions] Unreachable Clock Source kept on as sys.peer

2012-05-02 Thread Dave Hart
On Wed, May 2, 2012 at 11:28 AM, joerg.neul...@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

Re: [ntp:questions] Unreachable Clock Source kept on as sys.peer

2012-05-02 Thread joerg . neulist
Am Mittwoch, 2. Mai 2012 14:18:35 UTC+2 schrieb Dave Hart: I suspect you're seeing the same issue Miroslav Lichvar reported: http://bugs.ntp.org/1554 The fix first appeared in 4.2.7p58 and was later backported to 4.2.6p4. This seems to be the case. We will try an update. Thank you very

Re: [ntp:questions] FreeBSD and SureGPS

2012-05-02 Thread E-Mail Sent to this address will be added to the BlackLists
fRANz wrote: I played with a Sure GPS board Is it sending only one sentence? ntpd 4.2.6p2 from FreeBSD packages; You might also try a more recent version: http://ntp.org/downloads.html remote refid st t whn poll rchdly offset jitter