[ntp:questions] "ntpd -q" is slow compared to ntpdate

eugenemil at sbcglobal.net eugenemil at sbcglobal.net
Tue Oct 14 22:11:53 UTC 2008

The following argument can be made in favor of running ntpd -gq:
Suppose you want to reduce the time offset to (nearly) zero as rapidly
as possible on start-up and this causes you to be dissatisfied with
the behavior of ntpd when it it starts up and calculates an initial
offset of slightly less than the default step threshold of 128ms.  If
you run "ntpd -g" with something like "tinker step 0.001" in the
configuration file to insure that a step will occur on start-up, then
you are stuck with that step threshold indefinitely. You might want to
run  ntpd twice -- the first time in "one-shot" mode with the tinker
in the config, and the second time with a different configuration file
lacking the tinker.

Gene Miller

More information about the questions mailing list