Date: Sun, 7 Aug 2016 22:25:25 -0400 From: Michael Butler <imb@protected-networks.net> To: Randy Bush <randy@psg.com>, FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: leapsecond file Message-ID: <8092297e-7a0a-12c4-e115-4ed81d28f123@protected-networks.net> In-Reply-To: <m2wpjs102b.wl%randy@psg.com> References: <m2wpjs102b.wl%randy@psg.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
> daily_ntpd_leapfile_enable="YES"
> daily_ntpd_avoid_congestion="NO"
>
> consulting the net of a thousand lies did not bring enlightenment.
> maybe someone here has a clue bat? thanks.
"Broken" as designed :-(
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>
imb
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8092297e-7a0a-12c4-e115-4ed81d28f123>