Date: Sun, 9 Jul 2017 19:11:05 +0100 From: RW <rwmaillists@googlemail.com> To: freebsd-questions@freebsd.org Subject: Re: Interpreting NTP status Message-ID: <20170709191105.52dd6d4f@gumby.homeunix.com> In-Reply-To: <BN6PR2001MB173053AB0FB5FA9322784E7680A80@BN6PR2001MB1730.namprd20.prod.outlook.com> References: <BN6PR2001MB173053AB0FB5FA9322784E7680A80@BN6PR2001MB1730.namprd20.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 9 Jul 2017 14:39:44 +0000 Carmel NY wrote: > A while back, I was receiving an error message about an outdated =E2=80= =9Cleap > second=E2=80=9D file. I Googled around and found an article that said to = put > the following in the =E2=80=9Crc.conf=E2=80=9D file to correct the problem I wouldn't bother. IIRC it's a cosmetic bug, the working leapfile may not get overwritten by a downloaded version if only the expiry date is changed, so you may get a few bogus warnings until you update your base system. Most of us don't even need the file, the information is supposed to come from an upstream time server, and even if that fails the worst case is that your clock jumps by a second every few years.=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170709191105.52dd6d4f>