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

Re: 20050322: EXEC stderr output getting into PIPE results?

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: Re: 20050322: EXEC stderr output getting into PIPE results?
  • Date: Tue, 22 Mar 2005 13:44:17 -0700
Steven,

>Date: Tue, 22 Mar 2005 14:28:21 -0600
>From: "Steven Danz" <address@hidden>
>Organization: Aviation Weather Center
>To: Steve Emmerson <address@hidden>
>Subject: Re: 20050322: EXEC stderr output getting into PIPE results?

The above message contained the following:

> Thanks.  What is interesting is that it doesn't show up in 6.0.14.  With 
> 6.0.14, the lsof shows
> the stderr for all the decoders going to the log file of pqact (which is 
> where we need it).
> Putting the stderr of the decoders to /dev/null will make it quite 
> difficult to find decoder
> problems, true?

Sorry.  I misspoke.  I should have said that if the standard error
stream in pqact(1) is NOT directed to a file, then it will be directed
to "/dev/null" in any child process.  Otherwise, the standard error
stream will be left alone.

Regards,
Steve Emmerson