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 13:23:16 -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: <20030722172316.GC17916@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20030722145702.GA17342@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 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. If you use just exec, then cygwin should do the right thing. cgf -- 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/