>>> In article < XXXX@XXXXX.COM >, XXXX@XXXXX.COM (Tripathi, Anurag) writes:
Anurag> Here is ntpq -crv output: ---- assID=0 status=c624 sync_alarm,
Anurag> sync_ntp, 2 events, event_peer/strat_chg, version="ntpd 4.2.0a"?,
Anurag> processor="i686", system="Linux/18.104.22.168-ws-symbol", leap=11,
Anurag> stratum=16, precision=-20, rootdelay=0.000, rootdispersion=10.965,
Anurag> peer=17460, refid=INIT, reftime=00000000.00000000 Thu, Feb 7 2036
Anurag> 11:58:16.000, poll=6, clock=0xc86f5eb1.a257a786, state=3,
Anurag> offset=9.887, frequency=0.000, noise=3.628, jitter=2.328,
Anurag> stability=0.000 ------
You are in state 3, which means you are not sync'd. Therefore, in this
case, ntpdc seems to be stating correct info.
Just because ntpq shows that you are sync'd to the remote system does not
mean that your ntpd is ready to announce to other systems that it is stable.
Anurag> As suggested earlier after 30mins 'ntpdc sysinfo' starts showing the
Anurag> correct information i.e. 'synched'.
By this time I bet ntpq -crv will show that your ntpd is in state 4, which
Anurag> But isn't 30mins too long a delay for show an information which ntpq
Anurag> declares within seconds?
Just to be thorough, I believe you are seeing the difference between "ntpd
is not in state 4 but knows who to believe" and "ntpd is in state 4 and
knows who to believe".