Nist.pl was a script that we found some time ago and was fairly reliable until the last time zone change. Found it on some link some time ago. Here is the information on the script (not important).
# http://www.zdo.com # ftp://hun.ece.drexel.edu/pub/cinar/nist* # ftp://ftp.cpan.org/pub/CPAN/authors/id/A/AO/AOCINAR/nist* # ftp://sunsite.unc.edu/pub/Linux/system/admin/timei/nist* (Referencing time-a.timefreq.bldrdoc.gov) But what is important is that it is doing the same thing. If the time server reports bad data it doesn't matter how many time servers you are running. It only goes to the backup if the primary has failed. So in your statement it wouldn't have mattered. BTW, the servers that had the problem were our local NTP servers. When the clock got skewed it screwed up a bunch of other clocks as well. Gary Smith -----Original Message----- From: John Hardin [mailto:[EMAIL PROTECTED] Sent: Thursday, July 29, 2004 5:22 PM To: Gary Smith Cc: Amnon; SpamAssassin list Subject: RE: Servers clock On Thu, 2004-07-29 at 17:02, Gary Smith wrote: > We found that it happened to us around daylight savings time. > Sometimes the application (nist.pl) that we got somewhere goes haywire > based on the return result from the navy servers. In our case it went > back to a few months. nist.pl?? Surely there's an NTP daemon for whatever platform you're using? Surely you're synchronizing your local timesource to at least two remote timesources? :) -- John Hardin KA7OHZ <[EMAIL PROTECTED]> Internal Systems Administrator voice: (425) 672-1304 Apropos Retail Management Systems, Inc. fax: (425) 672-0192 ----------------------------------------------------------------------- If you smash a computer to bits with a mallet, that appears to count as encryption in the state of Nevada. - CRYPTO-GRAM 12/2001 -----------------------------------------------------------------------
