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: marco at gmail dot com, cygwin at cygwin dot com, Anr Daemon <anrdaemon at yandex dot ru>
- Date: Tue, 23 Dec 2014 12:09:24 +0100
- Subject: Re: Exitcode is 0 when killing a cygwin initiated process via taskmanager
- Authentication-results: sourceware.org; auth=none
>> 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 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.
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