X-Spam-Check-By: sourceware.org Date: Thu, 30 Mar 2006 17:10:02 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: freopen irritates system-call/sh.exe Message-ID: <20060330151002.GJ20907@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <442BDED7 DOT 6020107 AT osc-es DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk 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 Note-from-DJ: This may be spam On Mar 30 14:56, Eric Blake wrote: > Jens Wilken osc-es.de> writes: > > > How does freopen-ing stdout and stderr affect subsequent "system" calls? > > It shouldn't have any effect on subsequent calls, other than that stderr > or stdout is mapped to a new underlying stream. There are other changes, > unrelated to freopen, that do affect consoles popping up or not (and by > the way, snapshot 20060329 flashes a console when cygrunsrv starts an This has nothing to do with the snapshot. It's the latest change to cygrunsrv which re-introduced the short flash. It's very simple. Either a console window flashes for a split-second, or you will never see a console window, but the console window is then unusable for output from the service application. There's no way around this for now. To not lose the output capability, you'll have to live with the flashing window. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/