Skip to content
Snippets Groups Projects
Commit 12702d1a authored by Adam Wujek's avatar Adam Wujek
Browse files

[BUG: #372] rootfs/etc/leap-seconds.list: update file with new expiration date 


There is no new leap second introduced.
Update the default URL do the leap second file.

Signed-off-by: default avatarAdam Wujek <dev_public@wujek.eu>
parent 90817949
Branches
No related merge requests found
Hide whitespace changes
Inline Side-by-side
Kconfig
+ 1
− 1
View file @ 12702d1a
...@@ -112,7 +112,7 @@ endchoice ...@@ -112,7 +112,7 @@ endchoice
config LEAPSEC_URL config LEAPSEC_URL
string "URL for a run-time replacement of leap seconds file" string "URL for a run-time replacement of leap seconds file"
default "ftp://ftp.boulder.nist.gov/pub/time/leap-seconds.list" default "https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.list"
depends on LEAPSEC_SOURCE_REMOTE_TRY || LEAPSEC_SOURCE_REMOTE_FORCE depends on LEAPSEC_SOURCE_REMOTE_TRY || LEAPSEC_SOURCE_REMOTE_FORCE
help help
tftp://, ftp://, http:// or https:// URLs are allowed. For https tftp://, ftp://, http:// or https:// URLs are allowed. For https
......
userspace/rootfs_override/etc/leap-seconds.list
+ 120
− 255
View file @ 12702d1a
# # ATOMIC TIME
# In the following text, the symbol '#' introduces # Coordinated Universal Time (UTC) is the reference time scale derived
# a comment, which continues from that symbol until # from The "Temps Atomique International" (TAI) calculated by the Bureau
# the end of the line. A plain comment line has a # International des Poids et Mesures (BIPM) using a worldwide network of atomic
# whitespace character following the comment indicator. # clocks. UTC differs from TAI by an integer number of seconds; it is the basis
# There are also special comment lines defined below. # of all activities in the world.
# A special comment will always have a non-whitespace #
# character in column 2. #
# # ASTRONOMICAL TIME (UT1) is the time scale based on the rate of rotation of the earth.
# A blank line should be ignored. # It is now mainly derived from Very Long Baseline Interferometry (VLBI). The various
# # irregular fluctuations progressively detected in the rotation rate of the Earth led
# The following table shows the corrections that must # in 1972 to the replacement of UT1 by UTC as the reference time scale.
# be applied to compute International Atomic Time (TAI) #
# from the Coordinated Universal Time (UTC) values that #
# are transmitted by almost all time services. # LEAP SECOND
# # Atomic clocks are more stable than the rate of the earth's rotation since the latter
# The first column shows an epoch as a number of seconds # undergoes a full range of geophysical perturbations at various time scales: lunisolar
# since 1 January 1900, 00:00:00 (1900.0 is also used to # and core-mantle torques, atmospheric and oceanic effects, etc.
# indicate the same epoch.) Both of these time stamp formats # Leap seconds are needed to keep the two time scales in agreement, i.e. UT1-UTC smaller
# ignore the complexities of the time scales that were # than 0.9 seconds. Therefore, when necessary a "leap second" is applied to UTC.
# used before the current definition of UTC at the start # Since the adoption of this system in 1972 it has been necessary to add a number of seconds to UTC,
# of 1972. (See note 3 below.) # firstly due to the initial choice of the value of the second (1/86400 mean solar day of
# The second column shows the number of seconds that # the year 1820) and secondly to the general slowing down of the Earth's rotation. It is
# must be added to UTC to compute TAI for any timestamp # theoretically possible to have a negative leap second (a second removed from UTC), but so far,
# at or after that epoch. The value on each line is # all leap seconds have been positive (a second has been added to UTC). Based on what we know about
# valid from the indicated initial instant until the # the earth's rotation, it is unlikely that we will ever have a negative leap second.
# epoch given on the next one or indefinitely into the #
# future if there is no next line. #
# (The comment on each line shows the representation of # HISTORY
# the corresponding initial epoch in the usual # The first leap second was added on June 30, 1972. Until the year 2000, it was necessary in average to add a
# day-month-year format. The epoch always begins at # leap second at a rate of 1 to 2 years. Since the year 2000 leap seconds are introduced with an
# 00:00:00 UTC on the indicated day. See Note 5 below.) # average interval of 3 to 4 years due to the acceleration of the Earth's rotation speed.
# #
# Important notes: #
# # RESPONSIBILITY OF THE DECISION TO INTRODUCE A LEAP SECOND IN UTC
# 1. Coordinated Universal Time (UTC) is often referred to # The decision to introduce a leap second in UTC is the responsibility of the Earth Orientation Center of
# as Greenwich Mean Time (GMT). The GMT time scale is no # the International Earth Rotation and reference System Service (IERS). This center is located at Paris
# longer used, and the use of GMT to designate UTC is # Observatory. According to international agreements, leap seconds should be scheduled only for certain dates:
# discouraged. # first preference is given to the end of December and June, and second preference at the end of March
# # and September. Since the introduction of leap seconds in 1972, only dates in June and December were used.
# 2. The UTC time scale is realized by many national #
# laboratories and timing centers. Each laboratory # Questions or comments to:
# identifies its realization with its name: Thus # Christian Bizouard: christian.bizouard@obspm.fr
# UTC(NIST), UTC(USNO), etc. The differences among # Earth orientation Center of the IERS
# these different realizations are typically on the # Paris Observatory, France
# order of a few nanoseconds (i.e., 0.000 000 00x s) #
# and can be ignored for many purposes. These differences #
# are tabulated in Circular T, which is published monthly #
# by the International Bureau of Weights and Measures # COPYRIGHT STATUS OF THIS FILE
# (BIPM). See www.bipm.org for more information. # This file is in the public domain.
# #
# 3. The current definition of the relationship between UTC #
# and TAI dates from 1 January 1972. A number of different # VALIDITY OF THE FILE
# time scales were in use before that epoch, and it can be # It is important to express the validity of the file. These next two dates are
# quite difficult to compute precise timestamps and time # given in units of seconds since 1900.0.
# intervals in those "prehistoric" days. For more information, #
# consult: # 1) Last update of the file.
# #
# The Explanatory Supplement to the Astronomical # Updated through IERS Bulletin C (https://hpiers.obspm.fr/iers/bul/bulc/bulletinc.dat)
# Ephemeris. #
# or # The following line shows the last update of this file in NTP timestamp:
# Terry Quinn, "The BIPM and the Accurate Measurement #
# of Time," Proc. of the IEEE, Vol. 79, pp. 894-905, #$ 3945196800
# July, 1991. <http://dx.doi.org/10.1109/5.84965> #
# reprinted in: # 2) Expiration date of the file given on a semi-annual basis: last June or last December
# Christine Hackman and Donald B Sullivan (eds.) #
# Time and Frequency Measurement # File expires on 28 December 2025
# American Association of Physics Teachers (1996) #
# <http://tf.nist.gov/general/pdf/1168.pdf>, pp. 75-86 # Expire date in NTP timestamp:
# #
# 4. The decision to insert a leap second into UTC is currently #@ 3975868800
# the responsibility of the International Earth Rotation and #
# Reference Systems Service. (The name was changed from the #
# International Earth Rotation Service, but the acronym IERS # LIST OF LEAP SECONDS
# is still used.) # NTP timestamp (X parameter) is the number of seconds since 1900.0
# #
# Leap seconds are announced by the IERS in its Bulletin C. # MJD: The Modified Julian Day number. MJD = X/86400 + 15020
# #
# See www.iers.org for more details. # DTAI: The difference DTAI= TAI-UTC in units of seconds
# # It is the quantity to add to UTC to get the time in TAI
# Every national laboratory and timing center uses the #
# data from the BIPM and the IERS to construct UTC(lab), # Day Month Year : epoch in clear
# their local realization of UTC. #
# #NTP Time DTAI Day Month Year
# Although the definition also includes the possibility #
# of dropping seconds ("negative" leap seconds), this has 2272060800 10 # 1 Jan 1972
# never been done and is unlikely to be necessary in the 2287785600 11 # 1 Jul 1972
# foreseeable future. 2303683200 12 # 1 Jan 1973
# 2335219200 13 # 1 Jan 1974
# 5. If your system keeps time as the number of seconds since 2366755200 14 # 1 Jan 1975
# some epoch (e.g., NTP timestamps), then the algorithm for 2398291200 15 # 1 Jan 1976
# assigning a UTC time stamp to an event that happens during a positive 2429913600 16 # 1 Jan 1977
# leap second is not well defined. The official name of that leap 2461449600 17 # 1 Jan 1978
# second is 23:59:60, but there is no way of representing that time 2492985600 18 # 1 Jan 1979
# in these systems. 2524521600 19 # 1 Jan 1980
# Many systems of this type effectively stop the system clock for 2571782400 20 # 1 Jul 1981
# one second during the leap second and use a time that is equivalent 2603318400 21 # 1 Jul 1982
# to 23:59:59 UTC twice. For these systems, the corresponding TAI 2634854400 22 # 1 Jul 1983
# timestamp would be obtained by advancing to the next entry in the 2698012800 23 # 1 Jul 1985
# following table when the time equivalent to 23:59:59 UTC 2776982400 24 # 1 Jan 1988
# is used for the second time. Thus the leap second which 2840140800 25 # 1 Jan 1990
# occurred on 30 June 1972 at 23:59:59 UTC would have TAI 2871676800 26 # 1 Jan 1991
# timestamps computed as follows: 2918937600 27 # 1 Jul 1992
# 2950473600 28 # 1 Jul 1993
# ... 2982009600 29 # 1 Jul 1994
# 30 June 1972 23:59:59 (2287785599, first time): TAI= UTC + 10 seconds 3029443200 30 # 1 Jan 1996
# 30 June 1972 23:59:60 (2287785599,second time): TAI= UTC + 11 seconds 3076704000 31 # 1 Jul 1997
# 1 July 1972 00:00:00 (2287785600) TAI= UTC + 11 seconds 3124137600 32 # 1 Jan 1999
# ... 3345062400 33 # 1 Jan 2006
# 3439756800 34 # 1 Jan 2009
# If your system realizes the leap second by repeating 00:00:00 UTC twice 3550089600 35 # 1 Jul 2012
# (this is possible but not usual), then the advance to the next entry 3644697600 36 # 1 Jul 2015
# in the table must occur the second time that a time equivalent to 3692217600 37 # 1 Jan 2017
# 00:00:00 UTC is used. Thus, using the same example as above: #
# # A hash code has been generated to be able to verify the integrity
# ... # of this file. For more information about using this hash code,
# 30 June 1972 23:59:59 (2287785599): TAI= UTC + 10 seconds # please see the readme file in the 'source' directory :
# 30 June 1972 23:59:60 (2287785600, first time): TAI= UTC + 10 seconds # https://hpiers.obspm.fr/iers/bul/bulc/ntp/sources/README
# 1 July 1972 00:00:00 (2287785600,second time): TAI= UTC + 11 seconds #
# ... #h 848434d5 570f7ea8 d79ba227 a00fc821 f608e2d4
#
# in both cases the use of timestamps based on TAI produces a smooth
# time scale with no discontinuity in the time interval. However,
# although the long-term behavior of the time scale is correct in both
# methods, the second method is technically not correct because it adds
# the extra second to the wrong day.
#
# This complexity would not be needed for negative leap seconds (if they
# are ever used). The UTC time would skip 23:59:59 and advance from
# 23:59:58 to 00:00:00 in that case. The TAI offset would decrease by
# 1 second at the same instant. This is a much easier situation to deal
# with, since the difficulty of unambiguously representing the epoch
# during the leap second does not arise.
#
# Some systems implement leap seconds by amortizing the leap second
# over the last few minutes of the day. The frequency of the local
# clock is decreased (or increased) to realize the positive (or
# negative) leap second. This method removes the time step described
# above. Although the long-term behavior of the time scale is correct
# in this case, this method introduces an error during the adjustment
# period both in time and in frequency with respect to the official
# definition of UTC.
#
# Questions or comments to:
# Judah Levine
# Time and Frequency Division
# NIST
# Boulder, Colorado
# Judah.Levine@nist.gov
#
# Last Update of leap second values: 8 July 2016
#
# The following line shows this last update date in NTP timestamp
# format. This is the date on which the most recent change to
# the leap second data was added to the file. This line can
# be identified by the unique pair of characters in the first two
# columns as shown below.
#
#$ 3676924800
#
# The NTP timestamps are in units of seconds since the NTP epoch,
# which is 1 January 1900, 00:00:00. The Modified Julian Day number
# corresponding to the NTP time stamp, X, can be computed as
#
# X/86400 + 15020
#
# where the first term converts seconds to days and the second
# term adds the MJD corresponding to the time origin defined above.
# The integer portion of the result is the integer MJD for that
# day, and any remainder is the time of day, expressed as the
# fraction of the day since 0 hours UTC. The conversion from day
# fraction to seconds or to hours, minutes, and seconds may involve
# rounding or truncation, depending on the method used in the
# computation.
#
# The data in this file will be updated periodically as new leap
# seconds are announced. In addition to being entered on the line
# above, the update time (in NTP format) will be added to the basic
# file name leap-seconds to form the name leap-seconds.<NTP TIME>.
# In addition, the generic name leap-seconds.list will always point to
# the most recent version of the file.
#
# This update procedure will be performed only when a new leap second
# is announced.
#
# The following entry specifies the expiration date of the data
# in this file in units of seconds since the origin at the instant
# 1 January 1900, 00:00:00. This expiration date will be changed
# at least twice per year whether or not a new leap second is
# announced. These semi-annual changes will be made no later
# than 1 June and 1 December of each year to indicate what
# action (if any) is to be taken on 30 June and 31 December,
# respectively. (These are the customary effective dates for new
# leap seconds.) This expiration date will be identified by a
# unique pair of characters in columns 1 and 2 as shown below.
# In the unlikely event that a leap second is announced with an
# effective date other than 30 June or 31 December, then this
# file will be edited to include that leap second as soon as it is
# announced or at least one month before the effective date
# (whichever is later).
# If an announcement by the IERS specifies that no leap second is
# scheduled, then only the expiration date of the file will
# be advanced to show that the information in the file is still
# current -- the update time stamp, the data and the name of the file
# will not change.
#
# Updated through IERS Bulletin C65
# File expires on: 28 December 2023
#
#@ 3912710400
#
2272060800 10 # 1 Jan 1972
2287785600 11 # 1 Jul 1972
2303683200 12 # 1 Jan 1973
2335219200 13 # 1 Jan 1974
2366755200 14 # 1 Jan 1975
2398291200 15 # 1 Jan 1976
2429913600 16 # 1 Jan 1977
2461449600 17 # 1 Jan 1978
2492985600 18 # 1 Jan 1979
2524521600 19 # 1 Jan 1980
2571782400 20 # 1 Jul 1981
2603318400 21 # 1 Jul 1982
2634854400 22 # 1 Jul 1983
2698012800 23 # 1 Jul 1985
2776982400 24 # 1 Jan 1988
2840140800 25 # 1 Jan 1990
2871676800 26 # 1 Jan 1991
2918937600 27 # 1 Jul 1992
2950473600 28 # 1 Jul 1993
2982009600 29 # 1 Jul 1994
3029443200 30 # 1 Jan 1996
3076704000 31 # 1 Jul 1997
3124137600 32 # 1 Jan 1999
3345062400 33 # 1 Jan 2006
3439756800 34 # 1 Jan 2009
3550089600 35 # 1 Jul 2012
3644697600 36 # 1 Jul 2015
3692217600 37 # 1 Jan 2017
#
# the following special comment contains the
# hash value of the data in this file computed
# use the secure hash algorithm as specified
# by FIPS 180-1. See the files in ~/pub/sha for
# the details of how this hash value is
# computed. Note that the hash computation
# ignores comments and whitespace characters
# in data lines. It includes the NTP values
# of both the last modification time and the
# expiration time of the file, but not the
# white space on those lines.
# the hash line is also ignored in the
# computation.
#
#h e76a99dc 65f15cc7 e613e040 f5078b5e b23834fe
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment