NAME¶

ntpleapfetch - leap-seconds file manager/updater

SYNOPSIS¶

ntpleapfetch


    [-46] [-c command] [-e expiry] [-f config] [-F] [-h]


        [-i interval] [-l] [L] [-p {4|6}] [-P logfacility] [-q]


        [-r retries] [-s source-url] [-t path] [-v] [-z path]


        [-Z] [leapfile] [-V | --version] [filename]

DESCRIPTION¶

ntpleapfetch will validate the file currently on the local system and if necessary, update 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.

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.

For cron-friendly behavior, define CRONJOB=1 in the crontab.

OPTIONS¶

-4

-6

-c

-e expiry

-f config

-F

-i interval

-h

-l

-L

-p {4|6}

-P logfacility

-q

-r retries

-s source-url

-t path

-v

-z path

-Z

-V, --version

leapfile

EXIT STATUS¶

One of the following exit values will be returned:

0 (EXIT_SUCCESS)

1 (EXIT_FAILURE)

2

AUTHORS¶

Timothe Litt