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: Wed, 17 May 2000 21:47:48 -0400 From: Jim Koermer <address@hidden> To: Doug Hunt <address@hidden> Subject: Re: troubles stopping ldm with ldmadmin on linux Doug, Unless this is something unique to linux, I'm not sure that this behavior is all that unusual. I've noticed it for quite some time on FreeBSD and AIX systems running LDM. Usually this occurs during the ingestion of a large McIDAS area file that may take some time to download completely. I assume that this could also happen with some of the larger grib files. You can check this by looking at the file sizes after doing the "ldmadmin stop". After the file in question completely downloads, the associated rpc.ldmd process will end. I've noticed that if a large (~25MB) file just started downloading after the stop, it can take several minutes for it to complete. -- James P. Koermer E-Mail: address@hidden Professor of Meteorology Office Phone: (603)535-2574 Natural Science Department Office Fax: (603)535-2723 Plymouth State College WWW: http://vortex.plymouth.edu/ Plymouth, NH 03264 Doug Hunt wrote: > > Hi all: I have recently been having troubles stopping LDM via 'ldmadmin > stop' on linux. The ldmadmin script seems to not check correctly if all > LDM kids are killed off. The result is that after an 'ldmadmin stop', > one must wait for a minute or so for all rpc.ldmd children to die. If > one tries 'ldmadmin start' during this time, it hangs... > > I have made a small patch to 'ldmadmin' which seems to clean up this > problem. Instead of just killing off the rpc.ldmd process group leader, > it kills off all the kids too. > > Attached is the new ldmadmin script. > > Regards, > > Doug Hunt > > -- > address@hidden > Software Engineer III > UCAR - COSMIC > Tel. (303) 497-2611 >