Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Date: Thu, 10 Jan 2002 18:12:20 -0500
From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com
Subject: Re: No stderr output
Message-ID: <20020110231220.GA32764@redhat.com>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <000d01c19a23$2fbbbc50$0b00a8c0@leopard> <3C3E1E91.E457FB9A@iee.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
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/