[ntp:questions] ntpd stays synced after loosing gps
nowhere at mail.ru
Wed May 11 11:48:21 UTC 2011
Just one more question :-)
After loosing sync, server should lower it's stratum so other servers can't
synchronize with it, but:
remote refid st t when poll reach delay offset
PPS(0) .PPSE. 0 l 153 8 0 0.000 5.051
GENERIC(0) .TSIP. 0 l 158 8 0 0.000 -6.027
associd=0 status=0028 leap_none, sync_unspec, 2 events, no_sys_peer,
version="ntpd 4.2.7p164 at 1.2483 Wed May 11 07:27:34 UTC 2011 (1)",
processor="UNKNOWN", system="QNX/6.5.0", leap=00, stratum=1,
precision=-10, rootdelay=0.000, rootdisp=9.456, refid=PPSE,
reftime=d174f4ad.2bb91753 Wed, May 11 2011 17:42:37.170,
clock=d174f549.8e4f7235 Wed, May 11 2011 17:45:13.555, peer=0, tc=3,
mintc=3, offset=5.051, frequency=219.166, sys_jitter=0.977,
clk_jitter=0.977, clk_wander=0.160, tai=33, leapsec=200601010000,
ind assid status conf reach auth condition last_event cnt
1 17646 8023 yes no none reject unreachable 2
2 17647 8023 yes no none reject unreachable 2
I see that stratum Is still = 1 and servers could take this server time.
2011/5/11 Dave Hart <davehart at gmail.com>
> On Wed, May 11, 2011 at 07:31 UTC, Miroslav Lichvar <mlichvar at redhat.com>
> > On Wed, May 11, 2011 at 05:17:14AM +0000, Dave Hart wrote:
> >> 2011/5/11 Николай Орехов <nowhere at mail.ru>:
> >> > Could you provide me link to this bug and fixes so I can make a patch?
> >> No, I'm afraid I can't.
> > I think it's the bug #1554, which was fixed only in 4.2.7.
> > https://bugs.ntp.org/show_bug.cgi?id=1554
> You're right, Miroslav, thanks. It wasn't so long ago, I must repress
> negative memories :)
> That message has the ntp_proto.c patches that went into 4.2.7p58,
> which resolved this bug. I suspect only the first hunk (adding a call
> to clock_select()) is needed.
> Dave Hart
> questions mailing list
> questions at lists.ntp.org
More information about the questions