Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Tue, 22 Jul 2003 13:23:16 -0400
From:	Christopher Faylor <cgf-idd AT cygwin DOT com>
To:	cygwin AT cygwin DOT 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 AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<uadb68wgz DOT fsf AT gnu DOT org> <20030722145702 DOT GA17342 AT redhat DOT com> <uvftu7cp5 DOT fsf AT gnu DOT org>
Mime-Version:	1.0
In-Reply-To:	<uvftu7cp5.fsf@gnu.org>
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/

- Raw text -