[Git][NTPsec/ntpsec][master] Doc update re. ntpd's hourly leapfile check

[Hal Murray (@hal.murray)]

Hal Murray pushed to branch master at NTPsec / ntpsec


Commits:
4076ff11 by Joachim Kross at 2024-05-25T23:02:22+00:00
Doc update re. ntpd's hourly leapfile check

Unlike the current documentation states, ntpd checks once per
hour whether a configured leap seconds file has changed, and
reloads it if it has. It is only some logging in connection
with this update check that gets emitted only during one such
hourly check per day.

- - - - -


2 changed files:

- docs/includes/misc-options.adoc
- docs/leap.adoc


Changes:

=====================================
docs/includes/misc-options.adoc
=====================================
@@ -81,7 +81,7 @@ and that file system links, symbolic or otherwise, should be avoided.
 +
 The _leapfile_ is scanned when +ntpd+ processes the +leapfile+
 directive or when +ntpd+ detects that _leapfile_ has changed. +ntpd+
-checks once a day to see if the _leapfile_ has changed.
+checks once an hour to see if the _leapfile_ has changed.
 
 +leapsmearinterval+ 'interval'::
   This *experimental* option is only available if ntpd was built


=====================================
docs/leap.adoc
=====================================
@@ -37,11 +37,12 @@ the https://www.ietf.org/timezones/data/leap-seconds.list[IETF]
 and installed using the
 link:miscopt.html#leapfile[leapfile] command. The file includes a list
 of historic leap seconds and the NTP time of insertion. It is parsed by
-the +ntpd+ daemon at startup and the latest leap time saved for future
-reference. Each time the clock is set, the current time is compared with
-the last leap time. If the current time is later than the last leap
-time, nothing further is done. If earlier, the leap timer is initialized
-with the time in seconds until the leap time and counts down from there.
+the +ntpd+ daemon at startup, and checked for updates once per hour
+thereafter, and the latest leap time saved for future reference. Each
+time the clock is set, the current time is compared with the last leap
+time. If the current time is later than the last leap time, nothing
+further is done. If earlier, the leap timer is initialized with the time
+in seconds until the leap time and counts down from there.
 When the leap timer is less than one month, a pending leap condition
 exists until the end of the current month. If the leapseconds file is
 present, the leap bits for reference clocks and downstratum servers are



View it on GitLab: https://gitlab.com/NTPsec/ntpsec/-/commit/4076ff1199899ce65ee8e6c2ae756b069f5f8d0d

-- 
View it on GitLab: https://gitlab.com/NTPsec/ntpsec/-/commit/4076ff1199899ce65ee8e6c2ae756b069f5f8d0d
You're receiving this email because of your account on gitlab.com.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ntpsec.org/pipermail/vc/attachments/20240525/23e00554/attachment-0001.htm>