leapsecond file

Kevin Oberman rkoberman at gmail.com
Mon Aug 8 04:44:56 UTC 2016


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: rkoberman at gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683

On Sun, Aug 7, 2016 at 7:31 PM, Randy Bush <randy at 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
> >>
> >> # grep ntp /etc/periodic.conf.local
> >> # 480.leapfile-ntpd
> >> daily_ntpd_leapfile_enable="YES"
> >> daily_ntpd_avoid_congestion="NO"
> >
> > For whatever reason, /etc/periodic/daily/480.leapfile-ntpd enters the
> > check phase on every invocation (daily), sleeps some random time less
> > than one day (if "avoid_congestion" true) and then decides that the file
> > is too young to replace (the current file expires June 1st, 2017). Logs
> > that to syslog .. rinse and repeat .. every day .. <sigh>
>
> /me is not understanding
>
> # grep expires /var/db/ntpd.leap-seconds.list
> #       File expires on:  1 Jun 2016
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
>


More information about the freebsd-stable mailing list