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 16:04:44 -0400 (EDT) From: Jeff Masters <address@hidden> To: Devin Kramer <address@hidden> Subject: Re: troubles stopping ldm with ldmadmin on linux I have the same trouble on my Slackware linux boxes, my pqexpire and some of my rpc.ldmd processes don't die for many minutes. I find that even a manual kill -9 to the slow-to-die rpc.ldmd and pqexpire jobs will not make them exit, you just have to wait up to 8 minutes for them to die. On our Solaris box, everything exits immediately. ------------------------------------------------------------------------------ Dr. Jeff Masters (address@hidden) ( ) Chief Meteorologist /\ Home of the ( ) The Weather Underground, Inc. /\ / \ /\ /\ ( ) P.O. Box 3605 / \/ \/ \ /\ / \ ------ Ann Arbor, MI 48106-3605 ______/ / \/ \_ \\\\\ 734-994-8824 (voice) Weather Underground \`\`\ 734-994-8919 (fax) http://www.wunderground.com On Wed, 17 May 2000, Devin Kramer wrote: > Doug, > > Although a minute or so is a bit long I don't think it is strange to see > some of the rpc.ldmd children hanging on after a stop. I believe b/c > some of these are UDP connections they will not necessarily die > instantly. I could have the TCP and UDP thing backwards but I could > swear that one or the other suffers from this. I see it on our Solaris > 2.6 box quit often. Our wait time is more like 10-15 seconds but we > often find we need to wait a bit between ldmadmin stop's and ldmadmin > start's or it will just hang. If as you say it is more like minutes > then maybe there is some other issue. > > my $.02 > Devin > > -- > -------------------------------------------------------- > Programmer Analyst Department of Atmospheric Science > University of California Los Angeles > PH:(310)825-2418 FAX:(310)206-5219 > http://www.atmos.ucla.edu/geninfo/comp/how_to.html > -------------------------------------------------------- > > >