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.
>From: Tom Yoksas <address@hidden> >Organization: Unidata Program Center/UCAR >Keywords: 200412302001.iBUK1rlI005807 LDM clock Hi David, First, I hope that you have been having a relaxing holiday season! Please say hit to folks at UFRJ for me... it is hard for me to believe that it was three and a half months ago that I was in Brazil. Time is flying too fast!! Secondly, Steve Chiswell was looking at the real time stats being reported by brisa.meteoro.ufrj.br, when he noticed that the clock on brisa is 17 years in the future. I verified this for myself: [ldm@brisa ldm]$ date -u Fri Dec 31 21:32:28 UTC 2021 When the clock on the receiving machine is in advance of the clock on machines sending data, there will be significant data loss upon LDM stop and restart. For brisa, no data would flow until the time differenc between it and the upstream elapses -- 17 years! Could you look into getting brisa's clock straightened out? Thanks! Have a great New Years... Ciao, Tom -- +-----------------------------------------------------------------------------+ * Tom Yoksas UCAR Unidata Program * * (303) 497-8642 (last resort) P.O. Box 3000 * * address@hidden Boulder, CO 80307 * * Unidata WWW Service http://www.unidata.ucar.edu/ * +-----------------------------------------------------------------------------+