The "exec" before the second invocation of /bin/bash means that
this replaces the first bash, rather than having the first bash
wait for it to finish. Thus, you should not end up with two copies
of bash in memory. (This depends, of course, on the correct
implementation of the exec() functions in the cygwin1.dll)
/John Vincent.
Than this is a cygwin-bug?
(now i remember what exec means, isn't there an exec() in perl, too?)

i definitly get 2 bash.exe in the NT-taskmanager, and the first bash.exe keeps holding a handle to it's current dir.


--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/

Reply via email to