This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
=============================================================================== Robb Kambic Unidata Program Center Software Engineer III Univ. Corp for Atmospheric Research address@hidden WWW: http://www.unidata.ucar.edu/ =============================================================================== ---------- Forwarded message ---------- Date: Mon, 29 Nov 1999 11:27:05 -0700 From: Mike Schmidt <address@hidden> To: Harry Edmon <address@hidden> Subject: Re: Re[2]: 19991128: thelma's clock Harry, I think the time on thelma and other Unidata IDD nodes is good. We're sync'ed to two stratum 1 hosts on the internet (dec.com and navy.mil) and most of the LDM nodes here are sync'ed to thelma. Our product times look good to me; Nov 29 18:16:54 pqutil: 230 19991129181954.039 IDS|DDPLUS 566 SMBY01 UMMN 291800 RRA but the stuff coming from Alden looks to be off -- that's where the problem seems to be; Nov 29 18:16:53 pqutil: 92 19991129181953.915 IDS|DDPLUS 559 SPUS41 KWBC 291813 /pSPECI Robb will contact them to correct the problem. mike On Nov 29, 9:57am, Harry Edmon wrote: > Subject: Re[2]: 19991128: thelma's clock > Well, then someone upstream from thelma has the wrong time - I am seeing WMO > data from thelma with timestamps 3 minutes in the future. > ...