X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <26354920.post@talk.nabble.com> Date: Sat, 14 Nov 2009 15:26:22 -0800 (PST) From: aputerguy To: cygwin AT cygwin DOT com Subject: Re: How to capture stderr of dos process running in bash shell?? In-Reply-To: <4AFF05F3.5060706@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <26341304 DOT post AT talk DOT nabble DOT com> <4AFE14EB DOT 5020305 AT gmail DOT com> <20091114185556 DOT GA15089 AT ednor DOT casa DOT cgf DOT cx> <4AFF05F3 DOT 5060706 AT gmail DOT com> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Dave Korn writes: >Christopher Faylor wrote: >> >> Although, hmm, on rereading it isn't clear that the output shows up on >> the screen. It sounds like the DOS program just might not differentiate >> between stdout and stderr. Yes the output (both stderr and stdout) appear on screen > I checked: you can't redirect its error output at all, even in a genuine >cmd.exe shell with cygwin having nothing to do with it. It must indeed be >using the console directly. Curiouser and curiouser... it >links msvcrt.dll and imports printf and wprintf, but then it goes and actually >does everything the hard way with lowlevel console i/o in unicode. How peculiar. Strange. What is meant then by this sentence included in the help: "SubInAcl error messages are sent to the Standard error." -- View this message in context: http://old.nabble.com/How-to-capture-stderr-of-dos-process-running-in-bash-shell---tp26341304p26354920.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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