Date: Wed, 24 Aug 2016 14:21:41 -0700 From: Andreas Ott <andreas@naund.org> To: Ian Lepore <ian@freebsd.org> Cc: Andreas Ott <andreas@naund.org>, Kevin Oberman <rkoberman@gmail.com>, Randy Bush <randy@psg.com>, FreeBSD Stable <freebsd-stable@freebsd.org>, Cy Schubert <cy@freebsd.org> Subject: Re: leapsecond file Message-ID: <20160824142141.G1223@naund.org> In-Reply-To: <1472070074.1430.39.camel@freebsd.org>; from ian@freebsd.org on Wed, Aug 24, 2016 at 02:21:14PM -0600 References: <m2wpjs102b.wl%randy@psg.com> <8092297e-7a0a-12c4-e115-4ed81d28f123@protected-networks.net> <m2a8gom1no.wl%randy@psg.com> <CAN6yY1vKqs70SjcN57b19LmAnJcHkV3KEPTR%2B=HZhjqc6A4rbg@mail.gmail.com> <20160823224030.A9828@naund.org> <1472070074.1430.39.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 files, or the value is getting modified before it's > commited to the freebsd repos. (I'm adding Cy to the CC list, since he > committed them.) The beauty of standards is, that there are too many to chose from. These seem to be the three top sources of the file (lmgtfy), and while they might agree in the actual leapsecond data, the meta information in it is very different. fetch -m --no-passive ftp://tycho.usno.navy.mil/pub/ntp/leap-seconds.list fetch https://www.ietf.org/timezones/data/leap-seconds.list fetch https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.list [root@mon /tmp]# ls -la *list -rw-r--r-- 1 root wheel 10384 Mar 14 18:33 ietf-leap-seconds.list -rw-r--r-- 1 root wheel 8795 Jul 6 14:13 navy-leap-seconds.list -rw-r--r-- 1 root wheel 4920 Jul 6 14:37 obspm-leap-seconds.list [root@mon /tmp]# wc *list 249 1960 10384 ietf-leap-seconds.list 220 1657 8795 navy-leap-seconds.list 117 881 4920 obspm-leap-seconds.list [root@mon /tmp]# egrep -e Update\|expires\|^'#\$'\|^'#@' *list ietf-leap-seconds.list:# Last Update of leap second values: 5 January 2015 ietf-leap-seconds.list:#$ 3629404800 ietf-leap-seconds.list:# Updated through IERS Bulletin C51 ietf-leap-seconds.list:# File expires on: 28 December 2016 ietf-leap-seconds.list:#@ 3691872000 navy-leap-seconds.list:# Last Update of leap second values: 6 Jul 2016 navy-leap-seconds.list:#$ 3676752000 navy-leap-seconds.list:# Updated through IERS Bulletin C 52 navy-leap-seconds.list:# File expires on: 1 Jun 2017 navy-leap-seconds.list:#@ 3705264000 obspm-leap-seconds.list:# Updated through IERS Bulletin C (ftp://hpiers.obspm.fr/iers/bul/bulc/bulletinc.dat) obspm-leap-seconds.list:#$ 3676752000 obspm-leap-seconds.list:# File expires on 28 June 2017 obspm-leap-seconds.list:#@ 3707596800 [root@mon /tmp]# For now, the following workaround did get me a current file that ended up in /var/db/ after being downloaded to /var/run/ . IMHO, I have bought myself some time that this either gets fixed upstream, or until I need to keep my own site copy of the file on a web server that I'm responsible to update every 5.95 months. [root@mon /tmp]# grep leap /etc/rc.conf ntp_leapfile_fetch_opts="-m --no-passive" ntp_leapfile_sources="ftp://tycho.usno.navy.mil/pub/ntp/leap-seconds.list" [root@mon /tmp]# -andreas -- Andreas Ott K6OTT +1.408.431.8727 andreas@naund.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160824142141.G1223>