Re: why doesn't "exec" replace current executable w/new

[Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>]

On Mon, Nov 06, 2006 at 11:51:20AM -0000, Dave Korn wrote:
>On 06 November 2006 11:46, Linda Walsh wrote:
>>So why the top level bash?  Is there anything the parent bash can do
>>that the child bash cannot?
>
>The obvious WAG would be "wait for SIGCHLD, meaningfully" :)

Well, there's that, and there's also the fact that Cygwin has to emulate
exec.  It's not a Windows function.  There is no way to tell, e.g., a
Windows command shell to keep waiting for a new process that has been
execed without keeping the old one around.

See CreateProcess and the WaitFor* functions.

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/