This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Exitcode is 0 when killing a cygwin initiated process via taskmanager
- From: - <lopiuh at googlemail dot com>
- To: cygwin at cygwin dot com, anrdaemon at yandex dot ru
- Date: Tue, 23 Dec 2014 03:33:57 +0100
- Subject: Re: Exitcode is 0 when killing a cygwin initiated process via taskmanager
- Authentication-results: sourceware.org; auth=none
Hi,
>> Any idea how to solve (get the "canceled" exit code? Remember: The
>> script continues like a normal finish of the command)
> What do you mean by "canceled" exit code, pretty please?
oh, any exitcode <> 0 would be nice. Sending sigkill on debian gives a 137.
The point is, I rely on having a successfully executed command, if
exitcode is 0. In this case command is terminated, left garbage and
did not do its job and I go on like everything would be fine. How
should error checking care about such a condition / state?
Any ideas? And by the way, is such a condition in pure GNU/Linux
producible? Sigkill is quite brute force exit isn't it?
Thanks
--
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