Re: leapsecond file

2016-08-25 Thread Cy Schubert
In message <20160825001624.h1...@naund.org>, Andreas Ott writes: > Hi, > > On Wed, Aug 24, 2016 at 06:55:37PM -0700, Cy Schubert wrote: > > The file was obtained from USNO. Except for a $FreeBSD$ and a minor > > spelling fix that was brought forward from r298087, the file was not > > altered in

Re: leapsecond file

2016-08-25 Thread Andreas Ott
Hi, On Wed, Aug 24, 2016 at 06:55:37PM -0700, Cy Schubert wrote: > The file was obtained from USNO. Except for a $FreeBSD$ and a minor > spelling fix that was brought forward from r298087, the file was not > altered in any way. One of the problems is that the minor spelling fix > invalidated

Re: leapsecond file

2016-08-24 Thread Cy Schubert
In message <1472070074.1430.39.ca...@freebsd.org>, Ian Lepore writes: > On Tue, 2016-08-23 at 22:40 -0700, Andreas Ott wrote: > > 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

Re: leapsecond file

2016-08-24 Thread Andreas Ott
Hi, On Wed, Aug 24, 2016 at 02:21:14PM -0600, Ian Lepore wrote: > It looks like part of the problem here is that the Last Update value IS > changing when the leap data itself is not. Our commit logs say the > files have been obtained from USNO. Either USNO is violating the > standard in their

Re: leapsecond file

2016-08-24 Thread Ian Lepore
On Tue, 2016-08-23 at 22:40 -0700, Andreas Ott wrote: > 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

Re: leapsecond file

2016-08-23 Thread Andreas Ott
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

Re: leapsecond file

2016-08-08 Thread Trond Endrestøl
On Mon, 8 Aug 2016 11:11+0900, Randy Bush wrote: > i get these on all fbsd 10.3 hosts > > Aug 7 04:13:06 cache0 ntpd[576]: leapsecond file > ('/var/db/ntpd.leap-seconds.list'): expired less than 68 days ago > > i have > > # grep ntp /etc/periodic.conf.local > # 480.leapfile-ntpd >

Re: leapsecond file

2016-08-08 Thread Randy Bush
> 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). i will be patient. probably wait for 11.1. thanks. randy ___ freebsd-stable@freebsd.org mailing list

Re: leapsecond file

2016-08-07 Thread Kevin Oberman
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). Kevin Oberman, Part time kid herder and retired Network Engineer E-mail:

Re: leapsecond file

2016-08-07 Thread Randy Bush
>> Aug 7 04:13:06 cache0 ntpd[576]: leapsecond file >> ('/var/db/ntpd.leap-seconds.list'): expired less than 68 days ago >> >> # grep ntp /etc/periodic.conf.local >> # 480.leapfile-ntpd >> daily_ntpd_leapfile_enable="YES" >> daily_ntpd_avoid_congestion="NO" > > For whatever reason,

Re: leapsecond file

2016-08-07 Thread Michael Butler
On 08/07/16 22:11, Randy Bush wrote: > i get these on all fbsd 10.3 hosts > > Aug 7 04:13:06 cache0 ntpd[576]: leapsecond file > ('/var/db/ntpd.leap-seconds.list'): expired less than 68 days ago > > i have > > # grep ntp /etc/periodic.conf.local > # 480.leapfile-ntpd >