# SOME DESCRIPTIVE TITLE # Copyright (C) YEAR The FreeBSD Project # This file is distributed under the same license as the FreeBSD Documentation package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: FreeBSD Documentation VERSION\n" "POT-Creation-Date: 2022-02-01 09:21-0300\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "Language: \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. type: YAML Front Matter: description #: documentation/content/en/articles/leap-seconds/_index.adoc:1 #, no-wrap msgid "A short description of how leap seconds are handled on FreeBSD" msgstr "" #. type: Title = #: documentation/content/en/articles/leap-seconds/_index.adoc:1 #: documentation/content/en/articles/leap-seconds/_index.adoc:7 #, no-wrap msgid "FreeBSD Support for Leap Seconds" msgstr "" #. type: Plain text #: documentation/content/en/articles/leap-seconds/_index.adoc:39 msgid "'''" msgstr "" #. type: Title == #: documentation/content/en/articles/leap-seconds/_index.adoc:43 #, no-wrap msgid "Introduction" msgstr "" #. type: Plain text #: documentation/content/en/articles/leap-seconds/_index.adoc:47 msgid "" "A _leap second_ is an one second adjustment made at specific times of year " "to UTC to synchronize atomic time scales with variations in the rotation of " "the Earth. This article describes how FreeBSD interacts with leap seconds." msgstr "" #. type: Plain text #: documentation/content/en/articles/leap-seconds/_index.adoc:50 msgid "" "As of this writing, the next leap second will occur at 2015-Jun-30 23:59:60 " "UTC. This leap second will occur during a business day for North and South " "America and the Asia/Pacific region." msgstr "" #. type: Plain text #: documentation/content/en/articles/leap-seconds/_index.adoc:52 msgid "" "Leap seconds are announced by https://www.iers.org/IERS/EN/Home/home_node." "html[IERS] on https://datacenter.iers.org/data/latestVersion/16_BULLETIN_C16." "txt[Bulletin C]." msgstr "" #. type: Plain text #: documentation/content/en/articles/leap-seconds/_index.adoc:55 msgid "" "Standard leap second behavior is described in https://datatracker.ietf.org/" "doc/html/rfc7164#section-3[RFC 7164]. Also see man:time2posix[3]." msgstr "" #. type: Title == #: documentation/content/en/articles/leap-seconds/_index.adoc:57 #, no-wrap msgid "Default Leap Second Handling on FreeBSD" msgstr "" #. type: Plain text #: documentation/content/en/articles/leap-seconds/_index.adoc:62 msgid "" "The easiest way to handle leap seconds is with the POSIX time rules FreeBSD " "uses by default, combined with extref:{handbook}[NTP, network-ntp]. When " "man:ntpd[8] is running and the time is synchronized with upstream NTP " "servers that handle leap seconds correctly, the leap second will cause the " "system time to automatically repeat the last second of the day. No other " "adjustments are necessary." msgstr "" #. type: Plain text #: documentation/content/en/articles/leap-seconds/_index.adoc:64 msgid "" "If the upstream NTP servers do not handle leap seconds correctly, man:" "ntpd[8] will step the time by one second after the errant upstream server " "has noticed and stepped itself." msgstr "" #. type: Plain text #: documentation/content/en/articles/leap-seconds/_index.adoc:66 msgid "" "If NTP is not being used, manual adjustment of the system clock will be " "required after the leap second has passed." msgstr "" #. type: Title == #: documentation/content/en/articles/leap-seconds/_index.adoc:68 #, no-wrap msgid "Cautions" msgstr "" #. type: Plain text #: documentation/content/en/articles/leap-seconds/_index.adoc:72 msgid "" "Leap seconds are inserted at the same instant all over the world: UTC " "midnight. In Japan that is mid-morning, in the Pacific mid-day, in the " "Americas late afternoon, and in Europe at night." msgstr "" #. type: Plain text #: documentation/content/en/articles/leap-seconds/_index.adoc:74 msgid "" "We believe and expect that FreeBSD, if provided correct and stable NTP " "service, will work as designed during this leap second, as it did during the " "previous ones." msgstr "" #. type: Plain text #: documentation/content/en/articles/leap-seconds/_index.adoc:77 msgid "" "However, we caution that practically no applications have ever asked the " "kernel about leap seconds. Our experience is that, as designed, leap " "seconds are essentially a replay of the second before the leap second, and " "this is a surprise to most application programmers." msgstr "" #. type: Plain text #: documentation/content/en/articles/leap-seconds/_index.adoc:79 msgid "" "Other operating systems and other computers may or may not handle the leap-" "second the same way as FreeBSD, and systems without correct and stable NTP " "service will not know anything about leap seconds at all." msgstr "" #. type: Plain text #: documentation/content/en/articles/leap-seconds/_index.adoc:81 msgid "" "It is not unheard of for computers to crash because of leap seconds, and " "experience has shown that a large fraction of all public NTP servers might " "handle and announce the leap second incorrectly." msgstr "" #. type: Plain text #: documentation/content/en/articles/leap-seconds/_index.adoc:83 msgid "" "Please try to make sure nothing horrible happens because of the leap second." msgstr "" #. type: Title == #: documentation/content/en/articles/leap-seconds/_index.adoc:85 #, no-wrap msgid "Testing" msgstr "" #. type: Plain text #: documentation/content/en/articles/leap-seconds/_index.adoc:91 msgid "" "It is possible to test whether a leap second will be used. Due to the " "nature of NTP, the test might work up to 24 hours before the leap second. " "Some major reference clock sources only announce leap seconds one hour ahead " "of the event. Query the NTP daemon:" msgstr "" #. type: delimited block . 4 #: documentation/content/en/articles/leap-seconds/_index.adoc:95 #, no-wrap msgid "% ntpq -c 'rv 0 leap'\n" msgstr "" #. type: Plain text #: documentation/content/en/articles/leap-seconds/_index.adoc:99 msgid "" "Output that includes `leap_add_sec` indicates proper support of the leap " "second. Before the 24 hours leading up to the leap second, or after the " "leap second has passed, `leap_none` will be shown." msgstr "" #. type: Title == #: documentation/content/en/articles/leap-seconds/_index.adoc:101 #, no-wrap msgid "Conclusion" msgstr "" #. type: Plain text #: documentation/content/en/articles/leap-seconds/_index.adoc:104 msgid "" "In practice, leap seconds are usually not a problem on FreeBSD. We hope " "that this overview helps clarify what to expect and how to make the leap " "second event proceed more smoothly." msgstr ""