This document describes the use of the NTP Project’s update-leap
program.
This document applies to version 4.2.8p10 of update-leap
.
• update-leap Description: | Description | |
• update-leap Invocation: | Invoking update-leap |
Up: Top
update-leap
will validate the file currently on the local system
and if necessary, updates leap-second definition file.
Ordinarily, the file is found using the "leapfile" directive in
ntp.conf(5)
.
However, an alternate location can be specified on the command line.
If the file does not exist, is not valid, has expired, or is expiring soon, a new copy will be downloaded. If the new copy validates, it is installed and NTP is (optionally) restarted.
If the current file is acceptable, no download or restart occurs.
-c can also be used to invoke another script to perform administrative functions, e.g. to copy the file to other local systems. .PP This can be run as a cron job. As the file is rarely updated, and leap seconds are announced at least one month in advance (usually longer), it need not be run more frequently than about once every three weeks. .PP For cron-friendly behavior, define CRONJOB=1 in the crontab. .PP This script depends on$REQUIREDCMDS
This section was generated by AutoGen,
using the agtexi-cmd
template and the option descriptions for the update-leap
program.