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