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

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

>Date: Tue, 22 Mar 2005 12:52:12 -0700
>From: Unidata Support <address@hidden>
>Organization: NOAA/NWS/Aviation Weather Center
>To: address@hidden
>Subject: 20050322: EXEC stderr output getting into PIPE results?

The above message contained the following:

> Ran across an issue today where the stderr output of a csh script
> running from an EXEC in pqact ended up in a PIPE output file.  I
> saw the mail from Harry Edmon on March 3 2005, however the comment
> there was that this should only happen when pqact is not attached to
> a log file, and mine is (and is actively writing to it as I type).
> I'm currently running 6.2.1 and was wondering if Harry's patch (or
> something like it) was in 6.3.0

Yes.  That fix is in version 6.3.0.

> Thanks
> 
> Steven
> 
> -- 
> Steven Danz
> Senior Software Development Engineer
> Aviation Weather Center (NOAA/NWS/NCEP)
> 7220 NW 101st Terrace, Room 101
> Kansas City, MO 64153-2371
> 
> Email: address@hidden
> Phone: 816.584.7251
> Fax:   816.880.0650
> URL:   http://aviationweather.gov/
> 
> The opinions expressed in this message do not necessarily reflect those 
> of the National Weather Service, or the Aviation Weather Center.

Regards,
Steve Emmerson

> NOTE: All email exchanges with Unidata User Support are recorded in the
> Unidata inquiry tracking system and then made publicly available
> through the web.  If you do not want to have your interactions made
> available in this way, you must let us know in each email you send to us.