leapsecond file

Andreas Ott
Wed, 24 Aug 2016 05:40:30 -0000

On Sun, Aug 07, 2016 at 09:44:55PM -0700, Kevin Oberman
wrote:
> On 11.0-BETA4 I have:
> > grep expires /var/db/ntpd.leap-seconds.list
> #    File expires on:  1 Jun 2017
>
> But I see what you do on 10.3-RELEASE.  Looks like the update has not made
> it into 10 (an I would guess 9).

The flaw is in the internal versioning of files, it does fetch the newer
file from IETF and puts it into /var/run/ntpd.leap-seconds.list, but
although the expiry is newer, the FreeBSD onboard source version claims
to be newer in the 'last update date in NTP timestamp format' line ...

FreeBSD 10.3-RELEASE-p7 onboard source is in /etc/ntp/leap-seconds,
which gets copied to /var/db/ntpd.leap-seconds.list. The fetch
IETF file downloads to /var/run/ntpd.leap-seconds.list .


[root at mon ~]# egrep -e Update\|expires\|^'#\$' /etc/ntp/leap-seconds
#       Last Update of leap second values:  31 Dec 2015
#$       3660508800
#       Updated through IERS Bulletin C 50
#       File expires on:  1 Jun 2016
[root at mon ~]# egrep -e Update\|expires\|^'#\$'
/var/db/ntpd.leap-seconds.list
#       Last Update of leap second values:  31 Dec 2015
#$       3660508800
#       Updated through IERS Bulletin C 50
#       File expires on:  1 Jun 2016
[root at mon ~]# egrep -e Update\|expires\|^'#\$'
/var/run/ntpd.leap-seconds.list
#       Last Update of leap second values:   5 January 2015
#$       3629404800
#       Updated through IERS Bulletin C51
#       File expires on:  28 December 2016
[root at mon ~]#

with the end result that the file from /var/run/ never gets moved to /var/db/ .
The 480.leapfile-ntpd used by periodic calls the same rc file fetch and
comparison.

-andreas
--
Andreas Ott   K6OTT   +1.408.431.8727   andreas at naund.org