Greetings, Daniel Colascione! >> [cmd /c start foo not going into the background] >> It is not likely to change.
> What worries me isn't that the behavior changed, but that the new > behavior is weird. SIGINT doesn't work on processes spawned by cmd /c > start. > Try it yourself: > $ cmd /c start notepad > The weird thing is that cmd seems to have a PID, but sending a signal > to this process fails with ESRCH --- except for sending signal 0, > which succeeds. That's expected - non-cygwin applications don't know anything about signals. Even if, for example, SIGKILL would work on cmd (forcefully terminating it), Notepad will stay. -- WBR, Andrey Repin (anrdae...@freemail.ru) 10.05.2012, <12:28> Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
