10.3 base ntpd leap-seconds. list file expires 2016-06-01

[Andre Albsmeier]

On Fri, 13-May-2016 at 09:57:50 -0400, Ernie Luzar wrote:
> Trond Endrestøl wrote:
> > On Fri, 13 May 2016 13:01+0200, Andre Albsmeier wrote:
> > 
> >> On Fri, 13-May-2016 at 08:05:21 +0200, Trond Endrestøl wrote:
> >>> On Thu, 12 May 2016 17:55-0400, Ernie Luzar wrote:
> >>>
> >>>> New install of 10.3 from .iso file.
> >>>> On every boot of system get ntpd message saying
> >>>> /var/db/ntpd.leap-seconds.list file expires 2016-06-01.
> >>>>
> >>>> I'm running the base version of ntpd, the one that
> >>>> is included as part of the base system.
> >>>>
> >>>> This file should have been updated before 10.3 release was
> >>>> published to the public.
> >>>>
> >>>> Where do I get the updated ntpd.leap-seconds.list file contents
> >>>> to write to my /var/db/ntpd.leap-seconds.list file?
> >>> Add these lines to /etc/periodic.conf:
> >>>
> >>> daily_ntpd_leapfile_enable="YES"
> >>> daily_ntpd_avoid_congestion="YES"
> >> Hmm, I did this on 9.3 a while ago.. The new file (fetched from
> >> https://www.ietf.org/timezones/data/leap-seconds.list) has version
> >>
> >> #$	 3629404800
> >>
> >> and as expiry date:
> >>
> >> #@	3691872000
> >>
> >> The old file (the copy of /etc/ntp/leap-seconds in /var/db/ntpd.leap-seconds.list)
> >> has as version:
> >>
> >> #$       3660508800
> >>
> >> and as expiry date:
> >>
> >> #@      3673728000
> >>
> >> So the new file expires after the old file (which is good) but
> >> its version is lower than the version of the old file. Since
> >> /etc/rc.d/ntpd compares the versions it finally sticks with the
> >> old file...
> >>
> >> 	-Andre
> > 
> > Would it make more sense to use 
> > https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.list from the 
> > Earth orientation Center of the IERS?
> > 
> > That file has currently the following characteristics:
> > 
> > #$	3661632000
> > #	File expires on 28 December 2016
> > #@	3691872000
> > 
> 
> 
> https://www.ietf.org/timezones/data/leap-seconds.list
> Just checked this file and it expires on 28 December 2016.

But the version is older and /etc/rc.d/ntpd checks this.

Probably every "provider" got his own versioning system
and /etc/rc.d/ntpd should check the expiry instead.

> 
> service ntpd fetch downloads the same file as the base system has to 
> begin with.
> 
> I manually edited /var/db/ntpd.leap-seconds.list with the values from
> www.ietf.org/timezones/data/leap-seconds.list and did a

Did you fix the signature as well?

	-Andre

> service ntpd restart and the expire message did not show.
> 
> 

-- 
Never argue with an idiot. They drag you down to
their level, then beat you with their experience.