examples: switch chrony.conf examples to leapseclist

diff --git a/examples/chrony.conf.example2 b/examples/chrony.conf.example2
index bf2bbdda165c52b046109ded0154a81466df41d6..03e7d47b9a130dc0076ce0efcf4ef05771c8fff6 100644 (file)
--- a/examples/chrony.conf.example2
+++ b/examples/chrony.conf.example2
@@ -37,8 +37,8 @@ ntsdumpdir /var/lib/chrony
 # Insert/delete leap seconds by slewing instead of stepping.
 #leapsecmode slew
 
-# Get TAI-UTC offset and leap seconds from the system tz database.
-#leapsectz right/UTC
+# Set the TAI-UTC offset of the system clock.
+#leapseclist /usr/share/zoneinfo/leap-seconds.list
 
 # Specify directory for log files.
 logdir /var/log/chrony

diff --git a/examples/chrony.conf.example3 b/examples/chrony.conf.example3
index 6d84c0115058ec08288d776e1ab8133fd4812bb6..8d895d04590b02609a39feccff0a7f1e109d0ee6 100644 (file)
--- a/examples/chrony.conf.example3
+++ b/examples/chrony.conf.example3
@@ -126,11 +126,11 @@ ntsdumpdir /var/lib/chrony
 
 ! pidfile /var/run/chrony/chronyd.pid
 
-# If the system timezone database is kept up to date and includes the
-# right/UTC timezone, chronyd can use it to determine the current
-# TAI-UTC offset and when will the next leap second occur.
+# The system timezone database usually comes with a list of leap seconds and
+# corresponding TAI-UTC offsets.  chronyd can use it to set the offset of the
+# system TAI clock and have an additional source of leap seconds.
 
-! leapsectz right/UTC
+! leapseclist /usr/share/zoneinfo/leap-seconds.list
 
 #######################################################################
 ### INITIAL CLOCK CORRECTION