summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--recipes-support/ntp/files/ntp.conf.patch20
1 files changed, 17 insertions, 3 deletions
diff --git a/recipes-support/ntp/files/ntp.conf.patch b/recipes-support/ntp/files/ntp.conf.patch
index dbb7fb8..2d0fdd8 100644
--- a/recipes-support/ntp/files/ntp.conf.patch
+++ b/recipes-support/ntp/files/ntp.conf.patch
@@ -1,7 +1,7 @@
diff -Naur old/ntp.conf new/ntp.conf
---- old/ntp.conf 2017-01-17 12:00:15.560426583 -0600
-+++ new/ntp.conf 2017-01-17 12:02:11.968426337 -0600
-@@ -1,16 +1,44 @@
+--- old/ntp.conf 2017-02-01 12:51:59.766760466 -0600
++++ new/ntp.conf 2017-02-01 14:46:23.005239689 -0600
+@@ -1,16 +1,58 @@
-# This is the most basic ntp configuration file
# The driftfile must remain in a place specific to this
# machine - it records the machine specific clock error
@@ -36,10 +36,24 @@ diff -Naur old/ntp.conf new/ntp.conf
+
+# GPS Serial data reference (NTP0)
+# This sets the GPS 50 milliseconds slower than the PPS.
++# "true" says we don't trust the system clock.
++# If we are depending on the GPS for timing,
++# we don't want ntp to mark the GPS as a falseticker
++# because of a performance issue.
++# If the GPS is marked as a false ticker
++# due to a bad timestamp from the system
++# clock (possibly because the system was
++# too busy to process an interrupt),
++# the GPS will be ignored, and if we are
++# depending on the GPS for leap second, it
++# will not happen.
+server 127.127.28.0 true
+fudge 127.127.28.0 time1 0.050 refid GPS
+
+# GPS PPS reference (NTP2)
++# If we are depending on the PPS for timing,
++# we don't want ntp to mark the PPS as a falseticker
++# because of a performance issue.
+server 127.127.28.2 prefer true
+fudge 127.127.28.2 time1 0.000 refid PPS
+