Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <3C3E1E91.E457FB9A@iee.org>
Date: Thu, 10 Jan 2002 23:06:57 +0000
From: Don Sharp <dwsharp AT iee DOT org>
X-Mailer: Mozilla 4.78 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: gnuwin32 <cygwin AT cygwin DOT com>
Subject: Re: No stderr output
References: <000d01c19a23$2fbbbc50$0b00a8c0 AT leopard>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit



William S Fulton wrote:
> 
> Anything sent to stderr does not appear on the terminal. It seems to
> disappear into a black hole. I think it started when I was attempting to
> redirect stdout and stderr into the same file in the same order it appears
> on the console using something like
> runme 1>&2 > filename
> I tried all sorts of combinations and didn't get it to work :(
> 
> Any suggestions for bringing stderr back from the dead?
> Thanks.
> 

For Bourne style shells I use

runme > filename 2>&1

This redirects stdout first and then stderr to whereever stdout is
pointing.

Cheers

Don Sharp

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/