From: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder@niaid.nih.gov>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Date: Fri, 13 Nov 2009 16:12:10 -0500
Subject: RE: How to capture stderr of dos process running in bash shell??
Message-ID: <0105D5C1E0353146B1B222348B0411A2088722D749@NIHMLBX02.nih.gov>
References: <26341304.post@talk.nabble.com>  <20091113184304.GA18822@ednor.casa.cgf.cx>
In-Reply-To: <20091113184304.GA18822@ednor.casa.cgf.cx>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Christopher Faylor sent the following at Friday, November 13, 2009 1:43 PM
>On Fri, Nov 13, 2009 at 10:39:41AM -0800, aputerguy wrote:
>>I am trying to capture the error messages of 'subinacl.exe' (a dos
>>program included with Windows 2003 toolkit) which I am running from a bas=
h script.
>>
>>However both the stderr and stdout of the process seem to go to bash
>>stdout since redirecting bash stderr (2>) doesn't seem to have any effect.
>>
>>I assume this is because the dos process is running in a bash shell.
>
>More likely it is writing to the console directly, rather like writing
>to "/dev/tty" on UNIX.

See also the Cygwin User's Guide:
http://cygwin.com/cygwin-ug-net/using-effectively.html#id322908

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple