diff options
Diffstat (limited to 'recipes-support/ntp/files/ntpd-default')
| -rw-r--r-- | recipes-support/ntp/files/ntpd-default | 17 |
1 files changed, 11 insertions, 6 deletions
diff --git a/recipes-support/ntp/files/ntpd-default b/recipes-support/ntp/files/ntpd-default index 85b8041..4811f46 100644 --- a/recipes-support/ntp/files/ntpd-default +++ b/recipes-support/ntp/files/ntpd-default @@ -5,22 +5,27 @@ # This is needed if we are not using NTP servers. # NTP will not work with the GPS if the GPS is not # locked before starting. +# See /etc/default/gpsd for the states required. GPSD_REQUIRED=1 -# Number of seconds to wait before checking if -# the GPS has a lock. +# Number of seconds between testing for a GPS +# lock prior to calling ntpd. GPSD_WAIT_TIME=120 # Since the HW Clock could be off by a second or # so, our GPS might get marked as a false ticker # if we do not set the system clock to the GPS # first. The current correct way to do this -# according to the GPS doc is ntpd -gq +# according to the ntp doc is ntpd -gq -c conffile # which must be done before ntpd is started. +# conffile should exclude the local clock, so it is +# ignored while doing the initial sync. # ntpd -gq apparently does not work with the GPS -# when tested with the clock one day off and no -# ntpd. +# when tested with the clock more than one day off +# and no ntpd. The gps shared memory is never polled. +# # If there is a uBlox GPS present, the time is -# read from the GPS to initialize the system time. +# read from the GPS to initialize the system time +# before NTP is started. SET_SYSTEM_CLOCK=1 |