Promptly after fixing the
previus leapsecond file
I get the IERS Bulletin C number 49 today which states:
UTC TIME STEP
on the 1st of July 2015
A positive leap second will be introduced at the end of June 2015.
The sequence of dates of the UTC second markers will be:
2015 June 30, 23h 59m 59s
2015 June 30, 23h 59m 60s
2015 July 1, 0h 0m 0s
And I notice the IETF seems to update the canonical
leap-seconds file
about two months after the decision is made by the IERS.
It's a good thing ntpd starts complaining when the file is about to expire.
Update 2015-01-06:
An update was available from
ftp://time.nist.gov/ but only when
I connected over IPv6. An interesting form of IPv6 promotion. Notice the
difference in messages between the old file and the new file loading:
Jan 5 13:54:33 ritchie ntpd[13710]: leapsecond file ('/etc/ntp/leap-seconds.3644438400'): good hash signature
Jan 5 13:54:33 ritchie ntpd[13710]: leapsecond file ('/etc/ntp/leap-seconds.3644438400'): loaded, expire=2015-06-28T00:00Z ofs=35 (no entries after build date)
Jan 6 10:14:17 ritchie ntpd[26348]: leapsecond file ('/etc/ntp/leap-seconds.3629404800'): good hash signature
Jan 6 10:14:17 ritchie ntpd[26348]: leapsecond file ('/etc/ntp/leap-seconds.3629404800'): loaded, expire=2015-12-28T00:00Z last=2015-07-01T00:00Z ofs=36