diff options
Diffstat (limited to 'examples')
| -rw-r--r-- | examples/chrony.conf.example2 | 4 | ||||
| -rw-r--r-- | examples/chrony.conf.example3 | 8 |
2 files changed, 6 insertions, 6 deletions
diff --git a/examples/chrony.conf.example2 b/examples/chrony.conf.example2 index bf2bbdd..03e7d47 100644 --- 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 6d84c01..8d895d0 100644 --- 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 |