X-Spam-Check-By:	sourceware.org
Message-ID:	<454F2076.3010606@tlinx.org>
Date:	Mon, 06 Nov 2006 03:45:58 -0800
From:	Linda Walsh <cygwin AT tlinx DOT org>
User-Agent:	Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	why doesn't "exec" replace current executable w/new
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

I'm curious -- I thought "exec" was supposed to replace the currently
running executing image with the new image.

When I do an "exec" in "bash", it leaves the original bash.exe
in memory -- but only if the parent is at the top of its tree.

I.e. -- I can exec multiple bash's, but only the initial and the
newest child are kept -- intermediate generations exit.

So why the top level bash?  Is there anything the parent bash can
do that the child bash cannot?

Thanks,
-Linda


--
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 -