On Fri, Jun 09, 2017 at 04:28:07PM +0200, Mike Cook wrote: > > Le 9 juin 2017 à 12:52, Ashish Kurian <ashish...@gmail.com> a écrit : > > In my ntpq -p output, I see that the offset is around 70 milli second. How > > can I force my system clock to sync with the NTP server time. If I wait for > > a day, I know that the value will come down, but how can i get it synced > > without such long wait? > > Again, and I would say « as usual » , not enough info in the question to > make a reasonable guess. A bit like answering the question « how long is a > piece of sting? ». > That said, if you detected that just after starting ntpd, it probably means > the you need the « -g » option on startup.
You mean the -G option which was added in recent ntp versions? The -g option just temporarily disables the panic threshold and should't make a difference (unless the initial offset is larger than 1000 seconds). With older ntp versions it's recommended to run ntpdate -b before starting ntpd in order to speed up the initial synchronization. -- Miroslav Lichvar _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
