Here is ntpq -crv output: ---- assID=0 status=c624 sync_alarm, sync_ntp, 2 events, event_peer/strat_chg, version="ntpd 4.2.0a"?, processor="i686", system="Linux/2.6.13.4-ws-symbol", leap=11, stratum=16, precision=-20, rootdelay=0.000, rootdispersion=10.965, peer=17460, refid=INIT, reftime=00000000.00000000 Thu, Feb 7 2036 11:58:16.000, poll=6, clock=0xc86f5eb1.a257a786, state=3, offset=9.887, frequency=0.000, noise=3.628, jitter=2.328, stability=0.000 ------
As suggested earlier after 30mins 'ntpdc sysinfo' starts showing the correct information i.e. 'synched'. But isn't 30mins too long a delay for show an information which ntpq declares within seconds? More importantly is there anyway I can reduce/minimize this time lag? (some keyword or configuration?) This would be helpful! Regards, Anurag Other requested info: Ntpq version: "ntpq [EMAIL PROTECTED] Thu Mar 16 13:07:10 IST 2006 (1)" Ntpdc version: "ntpdc [EMAIL PROTECTED] Thu Mar 16 13:07:07 IST 2006 (1)" -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ronan Flood Sent: Monday, July 24, 2006 5:28 PM To: [email protected] Subject: [ntp:questions] Re: ntpdc 'sysinfo' output inconsistent with ntpq-p output On Sat, 22 Jul 2006 18:33:57 +0000, Harlan Stenn <[EMAIL PROTECTED]> wrote: > He's using iburst, so he probably got sync'd during the initial exchange. > > I do not understand the discrepancy between the ntpq output and the ntpdc > sysinfo output, but I really haven't thought about it all that much. I think what happens is that iburst allows ntpd quickly to sync to a source, but as noticed it doesn't remember the responses in the reach status, and doesn't declare itself synced to its clients until it has received the usual normal responses later. I think "ntpq -crv" would show similar info to ntpdc sysinfo in this state. -- Ronan Flood <[EMAIL PROTECTED]> working for but not speaking for Network Services, University of London Computer Centre (which means: don't bother ULCC if I've said something you don't like) _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions ________________________________________________________________________ This email has been scanned for computer viruses. ________________________________________________________________________ This email has been scanned for computer viruses. _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
