[ntp:questions] Observation with ntp4.2.8 at p4-request inputs

Charles Elliott elliott.ch at comcast.net
Thu Dec 10 11:55:11 UTC 2015

FWIIW, I have seen a similar phenomenon, only with one server.  If the time
server on my network stops dispensing time for some reason, the computers on
the LAN will still stay sync'ed to its last observation long after the reach
indicator goes to zero.  Not sure if that is right.

Charles Elliott

-----Original Message-----
From: questions
[mailto:questions-bounces+elliott.ch=comcast.net at lists.ntp.org] On Behalf Of
Sowmya Manapragada
Sent: Wednesday, December 9, 2015 10:26 PM
To: questions at lists.ntp.org
Subject: [ntp:questions] Observation with ntp4.2.8 at p4-request inputs

Hello All,
Just wanted to check if what I am observing with4.2.8p4 is as expected or I
missed out something because I don't see this with older 4.2.8p2/p3 :I have
a client having 2 NTP servers (both servers in my LAN ), client makes one as
a peer ( to which it is currently synced) and other as a candidate; the peer
(server) goes down, my client at least waited 7 to 8 min to reject this peer
server and choose the available one... Checked in Mein berg monitor tool
also and rv0 command ... The status word just don't show that client
rejected server until 7 to 8 minutes... Wire shark correctly shows no
packets exchanged between my clint and peer ( right from moment when server
which is down)..my client ntp.conf is standard with an iburst...
Thanks in advance
questions mailing list
questions at lists.ntp.org

More information about the questions mailing list