diff options
Diffstat (limited to 'recipes-core/multitech/config/config-mths/default/ntpd')
| -rw-r--r-- | recipes-core/multitech/config/config-mths/default/ntpd | 36 |
1 files changed, 0 insertions, 36 deletions
diff --git a/recipes-core/multitech/config/config-mths/default/ntpd b/recipes-core/multitech/config/config-mths/default/ntpd deleted file mode 100644 index a0d3bcf..0000000 --- a/recipes-core/multitech/config/config-mths/default/ntpd +++ /dev/null @@ -1,36 +0,0 @@ -ENABLED="no" - - -CONFIGFILE=/etc/ntp.conf - -# 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. -# See /etc/default/gpsd for the states required. -GPSD_REQUIRED=0 - -# 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 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 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 -# before NTP is started. -SET_SYSTEM_CLOCK=1 - |