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: Tue, 14 Dec 1999 11:50:09 -0600 (CST) From: Gilbert Sebenste <address@hidden> To: C. Vandersip <address@hidden> Subject: Re: Data latencies: could much of this be avoided? Chris, > Ok, I've changed my setup but I'm still getting IDS|DDPLUS|HDS latencies > over 15 minutes right now. Here's what my request looks like: > > 51 request IDS|DDPLUS ".*" ns2.rutgers.edu > 52 request HDS ".*" 165.230.4.74 > 53 request MCIDAS ".*" yang.sprl.umich.edu > 54 request FSL2 ".*" 141.213.23.51 > > Futhermore, I see only one pqact running: > > pluto.ldm> ps -aef | grep pqact > ldm 23340 23337 0 19:54:02 ? 12:28 pqact > > What do I need to correct? Nothing. If you re-started the LDM, you're fine. Ldm.pq does all the work. ******************************************************************************* Gilbert Sebenste ******** Internet: address@hidden (My opinions only!) ****** Staff Meteorologist, Northern Illinois University **** E-mail: address@hidden *** web: http://weather.admin.niu.edu ** Work phone: 815-753-5492 * *******************************************************************************