/usr/share/zoneinfo
This explorer reads the filesystem of the server it runs on, so /workspace/user isn't present here. Browsing and the terminal still work against this server's own disk from /.
# Allowance for leap seconds added to each time zone file. # This file is in the public domain. # This file is generated automatically from the data in the public-domain# NIST/IERS format leap-seconds.list file, which can be copied from# <https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.list># or via a less-secure protocol and with different comments and# less volatile last-modified and expiration timestamps, from# <ftp://ftp.boulder.nist.gov/pub/time/leap-seconds.list>.# For more about leap-seconds.list, please see# The NTP Timescale and Leap Seconds# <https://www.eecis.udel.edu/~mills/leap.html>. # The rules for leap seconds are specified in Annex 1 (Time scales) of:# Standard-frequency and time-signal emissions.# International Telecommunication Union - Radiocommunication Sector# (ITU-R) Recommendation TF.460-6 (02/2002)# <https://www.itu.int/rec/R-REC-TF.460-6-200202-I/>.# The International Earth Rotation and Reference Systems Service (IERS)# periodically uses leap seconds to keep UTC to within 0.9 s of UT1# (a proxy for Earth's angle in space as measured by astronomers)# and publishes leap second data in a copyrighted file# <https://hpiers.obspm.fr/iers/bul/bulc/Leap_Second.dat>.# See: Levine J. Coordinated Universal Time and the leap second.# URSI Radio Sci Bull. 2016;89(4):30-6. doi:10.23919/URSIRSB.2016.7909995# <https://ieeexplore.ieee.org/document/7909995>. # There were no leap seconds before 1972, as no official mechanism# accounted for the discrepancy between atomic time (TAI) and the earth's# rotation. The first ("1 Jan 1972") data line in leap-seconds.list# does not denote a leap second; it denotes the start of the current definition# of UTC. # All leap-seconds are Stationary (S) at the given UTC time.# The correction (+ or -) is made at the given time, so in the unlikely# event of a negative leap second, a line would look like this:# Leap YEAR MON DAY 23:59:59 - S# Typical lines look like this:# Leap YEAR MON DAY 23:59:60 + SLeap 1972 Jun 30 23:59:60 + SLeap 1972 Dec 31 23:59:60 + SLeap 1973 Dec 31 23:59:60 + SLeap 1974 Dec 31 23:59:60 + SLeap 1975 Dec 31 23:59:60 + SLeap 1976 Dec 31 23:59:60 + SLeap 1977 Dec 31 23:59:60 + SLeap 1978 Dec 31 23:59:60 + SLeap 1979 Dec 31 23:59:60 + SLeap 1981 Jun 30 23:59:60 + SLeap 1982 Jun 30 23:59:60 + SLeap 1983 Jun 30 23:59:60 + SLeap 1985 Jun 30 23:59:60 + SLeap 1987 Dec 31 23:59:60 + SLeap 1989 Dec 31 23:59:60 + SLeap 1990 Dec 31 23:59:60 + SLeap 1992 Jun 30 23:59:60 + SLeap 1993 Jun 30 23:59:60 + SLeap 1994 Jun 30 23:59:60 + SLeap 1995 Dec 31 23:59:60 + SLeap 1997 Jun 30 23:59:60 + SLeap 1998 Dec 31 23:59:60 + SLeap 2005 Dec 31 23:59:60 + SLeap 2008 Dec 31 23:59:60 + SLeap 2012 Jun 30 23:59:60 + SLeap 2015 Jun 30 23:59:60 + SLeap 2016 Dec 31 23:59:60 + S # UTC timestamp when this leap second list expires.# Any additional leap seconds will come after this.# This Expires line is commented out for now,# so that pre-2020a zic implementations do not reject this file.#Expires 2026 Dec 28 00:00:00 # Here are POSIX timestamps for the data in this file.# "#updated" gives the last time the leap seconds data changed# or, if this file was derived from the IERS leap-seconds.list,# the last time that file changed in any way.# "#expires" gives the first time this file might be wrong;# if this file was derived from the IERS leap-seconds.list,# this is typically a bit less than one year after "updated".#updated 1767698058 (2026-01-06 11:14:18 UTC)#expires 1798416000 (2026-12-28 00:00:00 UTC) # Updated through IERS Bulletin C (https://hpiers.obspm.fr/iers/bul/bulc/bulletinc.dat)# File expires on 28 December 2026