[ntp:questions] Re: ntpdc 'sysinfo' output inconsistent with ntpq-p output

Tripathi, Anurag Anurag.Tripathi at symbol.com
Mon Jul 24 15:11:11 UTC 2006

Here is ntpq -crv output: 
assID=0 status=c624 sync_alarm, sync_ntp, 2 events,
version="ntpd 4.2.0a"?, processor="i686",
system="Linux/", 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!


Other requested info:
Ntpq version: "ntpq 4.2.0a at 1.1196-r Thu Mar 16 13:07:10 IST 2006 (1)"
Ntpdc version: "ntpdc 4.2.0a at 1.1196-r Thu Mar 16 13:07:07 IST 2006 (1)"

-----Original Message-----
From: questions-bounces at lists.ntp.isc.org
[mailto:questions-bounces at lists.ntp.isc.org] On Behalf Of Ronan Flood
Sent: Monday, July 24, 2006 5:28 PM
To: questions at lists.ntp.isc.org
Subject: [ntp:questions] Re: ntpdc 'sysinfo' output inconsistent with
ntpq-p output

On Sat, 22 Jul 2006 18:33:57 +0000, Harlan Stenn <stenn at ntp.isc.org>

> He's using iburst, so he probably got sync'd during the initial
> I do not understand the discrepancy between the ntpq output and the
> 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

                      Ronan Flood <R.Flood at noc.ulcc.ac.uk>
                        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

questions mailing list
questions at lists.ntp.isc.org

This email has been scanned for computer viruses.

This email has been scanned for computer viruses.

More information about the questions mailing list