[ntp:questions] NTP not syncing immediately

Mike Cook michael.cook at sfr.fr
Sat Sep 19 09:06:04 UTC 2015


Can’t remember who the OP was…

The original ntp.conf, if that was all the entries reference just the local clock so why start ntp at all. There will be no disciplining anyway.

That aside I have just run some tests on a non windows machine and don’t see the issue, unless you are saying that you do not see the ‘*’ next to  the local clock. 
That I do not see on startup with your config.
It can be corrected by the following:

server 127.127.1.0 prefer  
fudge 127.127.1.0 stratum 0
restrict 127.127.1.0

Then on start up:

Sat Sep 19 08:56:43 UTC 2015
[ ok ] Starting ntpd (via systemctl): ntpd.service.

Sat Sep 19 08:56:44 UTC 2015
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*127.127.1.0     .LOCL.           0 l    -   64    1    0.000    0.000   0.002

there is sync with one second difference, but as I was polling with ntpq at 2 sec intervals it my be less than one second. Probably immediate.

Hope that helps.

Mike

> Le 18 sept. 2015 à 18:24, Kiss Gábor <kissg at niif.hu> a écrit :
> 
>> I want to sync immediately, my project requires to sync immediately as the
>> client is real time systems.
> 
> I'm afraid "real time system" means something else. :-)
> It is not related to wallclock time.
> https://en.wikipedia.org/wiki/Real-time_computing
> 
> Gabor
> _______________________________________________
> questions mailing list
> questions at lists.ntp.org
> http://lists.ntp.org/listinfo/questions

"The main function of a modern police force is filling in forms."


More information about the questions mailing list