Exitcode is 0 when killing a cygwin initiated process via taskmanager

[cyg Simple]

> 
> 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?!

Cygwin is a POSIX environment executing within the Windows OS environment.  If things happen outside of the Cygwin environment it cannot  detect those.  You must train your users to not use the Windows Task Manager to kill the process outside of the Cygwin environment.

The problem does not exist in Linux because there isn't an environment inside an environment so there isn't a chance to use the tools improperly.

--
cyg Simple


--
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