From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Exitcode is 0 when killing a cygwin initiated process via taskmanager
Date: Tue, 23 Dec 2014 11:37:00 -0000 [thread overview]
Message-ID: <549953CC.9030903@gmail.com> (raw)
In-Reply-To: <CAMhmPJ2RMoDhF0V=i4=TKtJ2bD_JeNOecUKzKN=0wR1PH8O-sQ@mail.gmail.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
next prev parent reply other threads:[~2014-12-23 11:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 11:09 -
2014-12-23 11:37 ` Marco Atzeri [this message]
2014-12-23 13:00 ` -
2014-12-23 19:47 ` cyg Simple
2014-12-24 1:56 ` -
-- strict thread matches above, loose matches on Subject: below --
2014-12-23 2:34 -
2014-12-23 7:41 ` Marco Atzeri
2014-12-23 0:38 -
2014-12-23 1:50 ` Andrey Repin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=549953CC.9030903@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).