This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]