Date: Thu, 02 Jun 2016 13:50:14 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 209970] /etc/rc.d/ntpd not updating /var/db/ntpd.leapseconds.list Message-ID: <bug-209970-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209970 Bug ID: 209970 Summary: /etc/rc.d/ntpd not updating /var/db/ntpd.leapseconds.list Product: Base System Version: 10.3-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: conf Assignee: freebsd-bugs@FreeBSD.org Reporter: mvharding@gmail.com '/etc/rc.d/ntpd fetch' does not update /var/db/ntpd.leapseconds.list. In looking at the file I have (on 10.3) vs. https://www.ietf.org/timezones/data/leap-seconds.list, it appears the the version number has gone backwards in the ietf.org version, but the expiry h= as moved forward. This is probably harmless, but caused me some confusion as = the file is now expired. If I type # service ntpd fetch ntp_src_leapfile version is 3660508800 ntp_db_leapfile version is 3660508800 not replacing /var/db/ntpd.leap-seconds.list with /etc/ntp/leap-seconds Within ntp leapfile expiry limit, initiating fetch fetching https://www.ietf.org/timezones/data/leap-seconds.list using existing /var/db/ntpd.leap-seconds.list The version and expiry on the ietf site are: #$ 3629404800 #@ 3691872000 and for the file in /var/db (sourced from somewhere in the FreeBSD tree, I think, it has FreeBSD svn info in it): #$ 3660508800 #@ 3673728000 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-209970-8>