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.
Shengting, > Yes. the LDM system did terminate gracefully. Good. It might have taken a while because the system was busy downloading the last hour's worth of data. > But I don't see a ldmd.pid file. The file "~ldm/ldmd.pid" is deleted by the command "ldmadmin stop" because it's no longer relevant. > What I meant was the message: > "Stopping the LDM server... > Waiting for the LDM server to terminate... > ....." > seems to suggest our computer has established connection to the LDM server. > This is part of the operation related to the first email I sent in which I > did " ldmadmin start", etc. The messages mean that the ldmadmin(1) script did send a SIGTERM to the LDM process group and that the script is now waiting for all the processes in that group to terminate. Regards, Steve Emmerson Ticket Details =================== Ticket ID: CMI-630638 Department: Support LDM Priority: Normal Status: Closed =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.