Date: Fri, 13 May 2016 13:01:43 +0200 From: Andre Albsmeier <Andre.Albsmeier@siemens.com> To: Trond =?iso-8859-1?Q?Endrest=F8l?= <Trond.Endrestol@fagskolen.gjovik.no> Cc: Ernie Luzar <luzar722@gmail.com>, questions@freebsd.org Subject: Re: 10.3 base ntpd leap-seconds. list file expires 2016-06-01 Message-ID: <20160513110143.GA99635@bali> In-Reply-To: <alpine.BSF.2.20.1605130802400.1421@mail.fig.ol.no> References: <5734FBDF.700@gmail.com> <alpine.BSF.2.20.1605130802400.1421@mail.fig.ol.no>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160513110143.GA99635>