[ntp:questions] NTP on local network

Richard B. Gilbert rgilbert88 at comcast.net
Sun Feb 17 14:44:42 UTC 2008


Danny Mayer wrote:
> venu gopal wrote:
> 
>>Hi,
>>
>>As per the ntpq output given, the initial offset is too high (in bold
>>below).
>>
>>ntpq> rv 12516
>>status=9014 reach, conf, 1 event, event_reach,
>>srcadr=MAIL, srcport=123, dstadr=192.168.4.18, dstport=123, leap=00,
>>stratum=2, precision=-6, rootdelay=31.250, rootdispersion=10932.175,
>>refid=DC1, reach=377, unreach=0, hmode=3, pmode=4, hpoll=6, ppoll=6,
>>flash=00 ok, keyid=0, ttl=0, *offset=3604309.724*, delay=0.240,
>>dispersion=20.390, jitter=11.206,
>>reftime=cb5bd42e.a7f3e6ed  Tue, Feb 12 2008 11:45:42.656,
>>org=cb5bd4bb.8004493a  Tue, Feb 12 2008 11:48:03.500,
>>rec=cb5bc6a7.2da250f8  Tue, Feb 12 2008 10:47:59.178,
>>xmt=cb5bc6a7.2d8f605a  Tue, Feb 12 2008 10:47:59.177,
>>filtdelay=     0.29    0.32    0.28    0.33    0.29    0.29    0.34
>>0.24,
>>filtoffset= 3604321 3604321 3604312 3604321 3604321 3604321 3604321
>>3604309,
>>filtdisp=     15.63   16.60   17.59   18.58   19.57   20.53   21.49
>>22.45
>>
>>
>>Before starting 'ntpd' use  'ntpdate' at the clients to nullify this initial
>>high
>>offset.
>>
> 
> 
> No, just add -g to the ntpd startup command line. There is no need for 
> ntpdate.
> 
> Danny

It's a losing battle Danny!  :-)




More information about the questions mailing list