> I am still unable to access the NIST ftp-site linked earlier in this thread.
There have been several URLs mentioned.
If you want:
ftp://time.nist.gov/pub/leap-seconds.list
Try
ftp://ftp.nist.gov/pub/time/leap-seconds.list
Any attempts at web/ftp-ing to time.nist.gov are very likely to
>
> > For the Paris Observatory and USNO files my program agrees with the SHA1s
> > in the files.
> > For the IETF file there seems to be one byte, a "0" at the start of the
> > third group of 8 hex characters missing.
>
>This is not a bug but a « feature ». From the ntpd leap hash checking
>
Hi,
On 12/18/2017 11:27 PM, Tom Van Baak wrote:
Rick,
The 53132A is a "12 digit/s" counter. Unless the frequency is really close to
10 MHz. Then it becomes a 11 digit/s counter. This is because it uses oversampling (IIRC,
200k samples/s) and it relies to some extent on statistics for its 12
Thank you Tom.
Very informative, sadly no simple answer to overcome the shortcoming. After
move, downsizing and age I imposed on my self a buy stop that I keep braking. I
did buy this year two 53132A's mainly because of the RS232 interface. Before I
had excellent results with a combination
David wrote:
For what it is worth, my 5370B run very hot, which forced me to check my
mains voltage* * *
it was consistently high.* * *
I managed to get the supply company to reduce the voltage by 5%.
Eliminating that small amount of extra dissipation won't get you
anywhere
> Le 20 déc. 2017 à 12:51, Anders Wallin a écrit :
>
> Hi all,
> So I'm doing the typical Wednesday thing you might do, that is writing a
> small script for checking the SHA1 checksum in leap-seconds.list files.
> I came up with [1] which produces output [2].
>
>
Martin Burnicki wrote:
> See also a summary at
> https://www.meinbergglobal.com/download/burnicki/the_ntp_leap_second_file.pdf
I saw that the leapseconds file provided by USNO is outdated, and FTP
access to the NIST sites has changed, so I've just updated the PDF
accordingly.
Martin
Martin Burnicki wrote:
> According to an email from Judah Levine (NIST) the current version of
> the leap second file is available via anonymous FTP from all public NIST
> NTP servers. A list of these servers and the status of each server is
> available at
> http://tf.nist.gov/tf-cgi/servers.cgi
>
Anders Wallin wrote:
> Thanks,
> I added the IANA URL to my list, and sent them an e-mail.
> I can't seem to reach the nist ftp-server - does it work for anyone?
Please note the global address time.nist.gov is resolved to a number of
public servers in a round-robin sequence. Some of the servers
John Hawkinson wrote:
> Umm, the presence of a copy of the IANA TZ distribution at
> https://www.ietf.org/timezones/ is not evidence of an "IETF leap-seconds
> list." This is bizarre, and probably a web server configuration error that
> even exists. The IETF is not involved in this list. I
Thanks,
I added the IANA URL to my list, and sent them an e-mail.
I can't seem to reach the nist ftp-server - does it work for anyone?
I re-named the output.txt so the link in my previous e-mail won't work.
The output now shows on the github repo frontpage:
Umm, the presence of a copy of the IANA TZ distribution at
https://www.ietf.org/timezones/ is not evidence of an "IETF leap-seconds list."
This is bizarre, and probably a web server configuration error that even
exists. The IETF is not involved in this list. I guess this shows why Google is
an
Hi all,
So I'm doing the typical Wednesday thing you might do, that is writing a
small script for checking the SHA1 checksum in leap-seconds.list files.
I came up with [1] which produces output [2].
For the Paris Observatory and USNO files my program agrees with the SHA1s
in the files.
For the
13 matches
Mail list logo