tp/leap-seconds 295461 2016-02-10 07:16:17Z cy $
> .
>
> 2016 Aug 18 18:26:07 [ntp.notice] mon leapsecond file ('/var/db/ntpd.leap-sec
> onds.list'): good hash signature
> 2016 Aug 18 18:26:07 [ntp.notice] mon leapsecond file ('/var/db/ntpd.leap-sec
> onds.list'): loaded, expir
that are hashed are the data and time stamps. Syslog shows that during the
last week the hash was considered OK on the file in 10.3-p7 with
$FreeBSD: releng/10.3/etc/ntp/leap-seconds 295461 2016-02-10 07:16:17Z cy $ .
2016 Aug 18 18:26:07 [ntp.notice] mon leapsecond file
('/var/db/ntpd.leap-seconds.li
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
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
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
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
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.loca
> 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
ber...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
On Sun, Aug 7, 2016 at 7:31 PM, Randy Bush <ra...@psg.com> wrote:
> >> Aug 7 04:13:06 cache0 ntpd[576]: leapsecond file
> ('/var/db/ntpd.leap-seconds.list'): expired less than 68 days ago
>
>> 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
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.loca
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
daily_ntpd_leapfile_enable="YES"
daily_ntpd_avoid_congestion="
12 matches
Mail list logo