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 10:57:02 -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:	<20030722145702.GA17342@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>
Mime-Version:	1.0
In-Reply-To:	<uadb68wgz.fsf@gnu.org>
User-Agent:	Mutt/1.4.1i

On Tue, Jul 22, 2003 at 10:30:52AM -0400, Sam Steingold wrote:
>So, how can I exit driver and have the shell notice that its child
>(driver) left a heir (runtime) and that the shell (bash & cmd) should
>wait for runtime to finish.

Am I reading this correctly?  You have two processes reading standard
input at the same time?  The expected behavior in that situation is that
it is unpredictable which process gets which keystroke.  You want the
parent of the parent of a process to know that there is a grandchild
process sitting around waiting for input and have the grandparent (bash
or cmd) wait for the grandchild to finish?

Under cygwin you'd accomplish this by having the parent process use one
of the "exec" calls.  There is no way to do what you want in a normal
Windows program.

cgf
--
Please use the resources at cygwin.com rather than sending personal email.
Special for spam email harvesters: send email to aaaspam AT sourceware DOT 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/

- Raw text -