This is the mail archive of the
cygwin
mailing list for the Cygwin project.
why doesn't "exec" replace current executable w/new
- From: Linda Walsh <cygwin at tlinx dot org>
- To: cygwin at cygwin dot com
- Date: Mon, 06 Nov 2006 03:45:58 -0800
- Subject: why doesn't "exec" replace current executable w/new
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/