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.
Hi Mark, re: > Hi Tom. I'll be a little more detailed with my reply tomorrow, but I > wanted to point out that the time shift is known and ntpdate is run once > a day early morning to reset the clock properly. Our experience is that it is much better to keep the clock synchronized using ntpd than running ntpdate out of cron. This is especially true on systems where LDM connections break and get reestablished. > I am at a loss to > explain why LDM2 isn't doing the same thing since they are identical > systems. We are unable to login to LDM2 using the login info you provided previously from LDM1... are you saying that the clock on LDM2 is much worse than on LDM1? Do you know what version of the LDM NCDC is running? There is possibility that the from time in the request from NCDC is causing the full set of data to not be requested. If NCDC is running a version of the LDM previous to 6.5.0, it is possibly the source of the problem being seen. Cheers, Tom **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: ZOC-298338 Department: Support LDM Priority: Urgent Status: Closed