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 10:18:26 -0700 From: Mike Schmidt <address@hidden> To: Harry Edmon <address@hidden> Subject: Re: 19991128: thelma's clock Harry, My first thought was that the clock on thelma might be off due to the time it was offline (because of the power supply failure) and it may not have adjusted on restart. The time seems to have set correctly after reboot; Nov 24 19:28:50 6D:thelma xntpd[191]: synchronized to 16.1.0.4, stratum=1 and seems to have stayed "synchronized" ever since based on log messages? mike On Nov 28, 7:21pm, Unidata Support wrote: > Subject: 19991128: thelma's clock > > ------- Forwarded Message > > >From: Harry Edmon <address@hidden> > >Subject: thelma's clock > >Organization: University of Washington > >Keywords: 199911282015.NAA08331 IDD thelma clock > > thelma's clock may be off. > -- > Dr. Harry Edmon E-MAIL: address@hidden > (206) 543-0547 FAX: (206) 543-0308 > Dept of Atmospheric Sciences > University of Washington, Box 351640, Seattle, WA 98195-1640 > > > ------- End of Forwarded Message > >-- End of excerpt from Unidata Support