Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 Date: Tue, 22 Jul 2003 17:27:05 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: subprocess i/o interaction with shell (bash&cmd): shells compete for input with user program! Message-ID: <20030722212705.GA26210@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20030722145702.GA17342@redhat.com> <20030722172316.GC17916@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Tue, Jul 22, 2003 at 04:41:18PM -0400, Sam Steingold wrote: >> * In message <20030722172316.GC17916@redhat.com> >> * On the subject of "Re: subprocess i/o interaction with shell (bash&cmd): shells compete for input with user program!" >> * Sent on Tue, 22 Jul 2003 13:23:16 -0400 >> * Honorable Christopher Faylor writes: >> >> On Tue, Jul 22, 2003 at 12:23:18PM -0400, Sam Steingold wrote: >> >> Under cygwin you'd accomplish this by having the parent process use >> >> one of the "exec" calls. >> > >> >nope. doesn't work either. >> >I get the same "input competition" when I use exec(). >> >> If you are using fork/exec, then sure, you'll get that. > >I am not using fork(). just plain exec(). Ok. Then you're not building cygwin applications apparently. Next assumption is that you're using the -mno-cygwin option. If the exec paradigm in cygwin was really broken, the mailing list would be filled with people complaining about that fact. cgf -- Please use the resources at cygwin.com rather than sending personal email. Special for spam email harvesters: send email to aaaspam@sourceware.org and be permanently blocked from mailing lists at sources.redhat.com -- 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/