From e48c5b532a26e094db24a7de44c33786860c7ae1 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Thu, 8 Feb 2024 15:28:21 -0800 Subject: [PROPOSED] Cite "The NTP Leap Second File" * tz-link.html: Cite leap-second.file website (thanks to Martin Burnicki). --- tz-link.html | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/tz-link.html b/tz-link.html index d41bbce6..a30f8427 100644 --- a/tz-link.html +++ b/tz-link.html @@ -1082,6 +1082,20 @@ In practice the two configurations also agree for timestamps before 1972 even though the historical situation is messy, partly because neither UTC nor TAI is well-defined for sufficiently old timestamps. +
  • The +NTP Leap Second File covers the text file +leap-seconds.list, which lists the currently known leap seconds. +The IERS maintains this file, and a copy is distributed by +tzdb for use by NTP implementations like +classic +ntpd +and NTPsec. +The tz database also distributes leap second +information in a differently-formatted leapseconds text file, +as well as in the "right" configuration in binary form; for +example, right/UTC can be used +by chrony, +another NTP implementation.
  • Leap Smear discusses how to gradually adjust POSIX clocks near a leap second so that they disagree with UTC by at most a @@ -1089,7 +1103,7 @@ half second, even though every POSIX minute has exactly sixty seconds. This approach works with the default tz "posix" configuration, is supported by -the NTP reference implementation, NTP implementations, supports conversion between UTC and smeared POSIX timestamps, and is used by major cloud service providers. However, according to -- 2.43.0