[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #CZC-252344]: capturing stderr from LDM PIPE command

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.

  • Subject: [LDM #CZC-252344]: capturing stderr from LDM PIPE command
  • Date: Fri, 03 Feb 2006 16:08:53 -0700
> Is there anyway to capture the stderr output
> of a program to which LDM products are being
> PIPED?

No because such decoders are executed by the pqact(1) process, which is 
executed by the LDM server, which is a daemon process and for which the 
standard output and standard error streams do not exist.  Consequently, 
decoders must make arrangements for logging messages.  They can use the ulog(1) 
facility that comes with the LDM package, or, if the decoder is a script, the 
ulogger(1) utility that also comes with the LDM package, or the logger(1) 
utility that comes with the operating system.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: CZC-252344
Department: Support LDM
Priority: Normal
Status: Closed