Hi Marco, I agree and I didn't want to rant. I just consider robustness and I can not rely on or guarantee that cygwin kill ist used. (It is the user of the Windows machine being creative ;-)
I scratch my head if we have a similar situation in GNU/Linux. If anything went havoc I so far supposed that exit code or abrupt script breakdown (stop) cares about not doing nasty things. So at the moment if you consider the OS or a user kills a process with Taskmanager we have to use another error handling in scripts at the moment. Is that true in GNU/Linux as well? What do you think? I can't find a clear answer in the www so far. If it is similar in GNU/Linux we have a general problem I suppose. If it is a cygwin thing, it is a feature which behaves different to the real posix world?! Greetings lopiuh -- 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
