From 823edc2d6be48e9dc2dffda2f44c8dea5b7fc1e6 Mon Sep 17 00:00:00 2001 From: John Klug Date: Fri, 13 Jan 2017 18:48:22 -0600 Subject: Add /etc/default/ntpd to the ntp configuration. --- recipes-support/ntp/files/ntpd-default | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 recipes-support/ntp/files/ntpd-default (limited to 'recipes-support/ntp/files/ntpd-default') diff --git a/recipes-support/ntp/files/ntpd-default b/recipes-support/ntp/files/ntpd-default new file mode 100644 index 0000000..85b8041 --- /dev/null +++ b/recipes-support/ntp/files/ntpd-default @@ -0,0 +1,26 @@ +# The GPSD_* parameters in this file are ignored +# if the uBlox GPS is not present. + +# Require a GPS lock/fix before starting NTP +# 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. +GPSD_REQUIRED=1 + +# Number of seconds to wait before checking if +# the GPS has a lock. +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 +# which must be done before ntpd is started. +# ntpd -gq apparently does not work with the GPS +# when tested with the clock one day off and no +# ntpd. +# If there is a uBlox GPS present, the time is +# read from the GPS to initialize the system time. +SET_SYSTEM_CLOCK=1 + -- cgit v1.2.3 From a439b62e1e91fbb6822e0e4a5b3714bd2e28b969 Mon Sep 17 00:00:00 2001 From: John Klug Date: Fri, 13 Jan 2017 19:24:21 -0600 Subject: Enhance the documentation for /etc/default/ntpd --- recipes-support/ntp/files/ntpd-default | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) (limited to 'recipes-support/ntp/files/ntpd-default') 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 -- cgit v1.2.3