Blame SOURCES/chrony-defconfig.patch

f132bc
diff -up chrony-3.2/examples/chrony.conf.example2.defconfig chrony-3.2/examples/chrony.conf.example2
f132bc
--- chrony-3.2/examples/chrony.conf.example2.defconfig	2017-09-15 08:32:09.000000000 +0200
f132bc
+++ chrony-3.2/examples/chrony.conf.example2	2017-09-18 12:48:08.688020942 +0200
f132bc
@@ -28,9 +28,6 @@ rtcsync
f132bc
 # Specify file containing keys for NTP authentication.
f132bc
 #keyfile /etc/chrony.keys
f132bc
 
f132bc
-# Get TAI-UTC offset and leap seconds from the system tz database.
f132bc
-#leapsectz right/UTC
f132bc
-
f132bc
 # Specify directory for log files.
f132bc
 logdir /var/log/chrony
f132bc
 
f132bc
--- chrony-3.4/examples/chrony.keys.example	2018-09-19 16:38:15.000000000 +0200
f132bc
+++ chrony-3.4/examples/chrony.keys.example	2017-09-15 08:32:09.000000000 +0200
f132bc
@@ -1,7 +1,6 @@
f132bc
-# This is an example chrony keys file.  It enables authentication of NTP
f132bc
-# packets with symmetric keys when its location is specified by the keyfile
f132bc
-# directive in chrony.conf(5).  It should be readable only by root and the
f132bc
-# user under which chronyd is running.
f132bc
+# This is an example chrony keys file.  It is used for NTP authentication with
f132bc
+# symmetric keys.  It should be readable only by root or the user to which
f132bc
+# chronyd is configured to switch to after start.
f132bc
 #
f132bc
 # Don't use the example keys!  It's recommended to generate random keys using
f132bc
 # the chronyc keygen command.