X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Fri, 13 Nov 2009 13:43:04 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: How to capture stderr of dos process running in bash shell?? Message-ID: <20091113184304.GA18822@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <26341304.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <26341304.post@talk.nabble.com> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com 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 bash 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. cgf -- 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