The IERS has issued Bulletin C54 which assures that no leap second will occur near 2018-01-01. Interestingly, the issue date 2017-07-06 in the txt version at [https://datacenter.iers.org/eop/-/somos/5Rgv/getTX/16/bulletinc-054.txt] differs from the issue date 2017-07-09 in the xml version at [https://datacenter.iers.org/eop/-/somos/5Rgv/latestXL/16/bulletinc-054.txt/x...] Michael Deckers. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
On 2017-07-10 09:51, Michael Deckers wrote BS -- please ignore. Sorry Michael Deckers. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Thanks, I pinged NIST about this, as they are the upstream provider for leap-seconds.list; we have not resolved the copyright issues for the corresponding IERS file.
Paul Eggert <eggert@cs.ucla.edu> wrote:
Thanks, I pinged NIST about this, as they are the upstream provider for leap-seconds.list;
Looks like NIST updated their file on Friday: $ curl ftp://ftp.nist.gov/pub/time/ dr-xr-xr-x 4 ftp ftp 4096 Dec 27 2016 clock_data dr-xr-xr-x 10 ftp ftp 4096 Feb 18 18:07 gps_data -r--r--r-- 1 ftp ftp 10654 Jul 08 15:10 leap-seconds.3676924800 -r--r--r-- 1 ftp ftp 10654 Jul 08 15:50 leap-seconds.list -r--r--r-- 1 ftp ftp 160 Jul 08 15:13 md5checksum dr-xr-xr-x 7 ftp ftp 4096 Dec 27 2016 software Tony. -- f.anthony.n.finch <dot@dotat.at> http://dotat.at/ - I xn--zr8h punycode Bailey: Variable 3 or 4, becoming westerly 4 or 5 later in north. Moderate. Showers. Good.
On 07/10/2017 11:34 AM, Tim Parenti wrote:
On 10 Jul 2017 12:38, Tony Finch wrote:
Looks like NIST updated their file on Friday: Must have been moments after I checked. Proposed patch attached.
Thanks, I installed that. By the way, I checked ftp://time.nist.gov/pub/leap-seconds.list just now, and it is still the old version for me. Perhaps it depends on the luck of the draw from round-robin DNS? Still, it's odd that you seem to be luckier than I. I contacted 216.229.0.179. I just now tried again and got 216.228.192.69, and it's also the old version. Are you using a particular IP address that you know is more up-to-date?
On 2017-07-10 13:26, Paul Eggert wrote:
On 07/10/2017 11:34 AM, Tim Parenti wrote:
On 10 Jul 2017 12:38, Tony Finch wrote:
Looks like NIST updated their file on Friday: $ curl ftp://ftp.nist.gov/pub/time/ dr-xr-xr-x 4 ftp ftp 4096 Dec 27 2016 clock_data dr-xr-xr-x 10 ftp ftp 4096 Feb 18 18:07 gps_data -r--r--r-- 1 ftp ftp 10654 Jul 08 15:10 leap-seconds.3676924800 -r--r--r-- 1 ftp ftp 10654 Jul 08 15:50 leap-seconds.list -r--r--r-- 1 ftp ftp 160 Jul 08 15:13 md5checksum dr-xr-xr-x 7 ftp ftp 4096 Dec 27 2016 software Must have been moments after I checked. Proposed patch attached. Thanks, I installed that. By the way, I checked ftp://time.nist.gov/pub/leap-seconds.list just now, and it is still the old version for me. Perhaps it depends on the luck of the draw from round-robin DNS? Still, it's odd that you seem to be luckier than I. I contacted 216.229.0.179. I just now tried again and got 216.228.192.69, and it's also the old version. Are you using a particular IP address that you know is more up-to-date?
He quoted the direct FTP site ftp://ftp.nist.gov/pub/time/ not the RR DNS time server sites ftp://time.nist.gov/pub/, which are busy and to which connects often fail, possibly because some of those RR DNS sites no longer support public FTP and/or provide leap-seconds.list (previously checked access to the target for each time server, not whether the service was accessible). -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
participants (5)
-
Brian Inglis -
Michael Deckers -
Paul Eggert -
Tim Parenti -
Tony Finch