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: Marco Atzeri <marco dot atzeri at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 23 Dec 2014 12:36:44 +0100
- Subject: Re: Exitcode is 0 when killing a cygwin initiated process via taskmanager
- Authentication-results: sourceware.org; auth=none
- References: <CAMhmPJ2RMoDhF0V=i4=TKtJ2bD_JeNOecUKzKN=0wR1PH8O-sQ at mail dot gmail dot com>
On 12/23/2014 12:09 PM, - wrote:
Using Taskmanager is brute force as cygwin dll can not act and correctly manage the exitcode
Hi,
thanks, but I do not agree. One element of the script was killed, not
the hoÃe script.
It was not killed in the proper cygwin way.
> It should be more robust. What I do now is: Read
stdout of the program (rsync) and only if I got the right footer of
rsync I rely on exitcode 0.
That is insane.
your opinion.
For me, it is simple: if you want a Unix like behavior use cygwin kill.
Otherwise propose a patch...
https://cygwin.com/acronyms/#PTC
Is it possible to kill the process of a script element in GNU and
having a returncode of 0 and a continuing script? If yes we can't use
returncodes at all anymore in shell scripts?
Thanks 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