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
Date:	Thu, 10 Jan 2002 18:12:20 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: No stderr output
Message-ID:	<20020110231220.GA32764@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<000d01c19a23$2fbbbc50$0b00a8c0 AT leopard> <3C3E1E91 DOT E457FB9A AT iee DOT org>
Mime-Version:	1.0
In-Reply-To:	<3C3E1E91.E457FB9A@iee.org>
User-Agent:	Mutt/1.3.23.1i

On Thu, Jan 10, 2002 at 11:06:57PM +0000, Don Sharp wrote:
>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.

If this doesn't do it, then I think the best plan is to find help from
another mailing list.  Basic shell questions are not really appropriate
here -- especially given the recent volume we've been experiencing.

cgf

--
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/

- Raw text -