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.
Justin, I think I found the problem. It's related to the addition of the command-string to some of pqact(1)'s log messages. Would you be willing to try another version? If so, then replace your LDM 6.4.3.0 with ftp://ftp.unidata.ucar.edu/pub/ldm/ldm-6.4.4.0.tar.Z If it fixes the extraneous logging messages, then I'll release it as version 6.4.4. Regards, Steve Emmerson ------- Original Message Date: Tue, 15 Nov 2005 12:57:26 -0500 From: Justin Cooke <address@hidden>To: Steve Emmerson <steve@uni data.ucar.edu> cc: address@hidden, Paula Freeman <address@hidden>, Scott Jacobs <address@hidden>, Jeff Ator <address@hidden> Subject: Re: Broken pipe Steve, Steve Emmerson wrote: >Justin, > >Does the decoder > > bin/decod_dcrast > >close its standard input stream? If so, what criteria does it use to >make that decision? > >Does the same decoder terminate after completely reading a data-product >on its standard input stream but before it reads an end-of-file on that >stream? > > I passed this along to Jeff and Scott who work with the decoders...here is their response: --- The GEMPAK-based decoders do not close the input data stream. They read from standard input. After a timeout (no data has arrived in X amount of time), the decoder does shut down. I don't know if the LDM is aware of the shut down or if the pipe remains open from the LDM end. --- Hopefully that answers your question, Justin ------- End of Original Message