From: - <lopiuh@googlemail.com>
To: marco@gmail.com, cygwin@cygwin.com, Anr Daemon <anrdaemon@yandex.ru>
Subject: Re: Exitcode is 0 when killing a cygwin initiated process via taskmanager
Date: Tue, 23 Dec 2014 13:00:00 -0000 [thread overview]
Message-ID: <CAMhmPJ1xDjhepMTO3x2_AF6xo5mA3i193qKXJ5znfax7_YDDCg@mail.gmail.com> (raw)
In-Reply-To: <CAMhmPJ2RMoDhF0V=i4=TKtJ2bD_JeNOecUKzKN=0wR1PH8O-sQ@mail.gmail.com>
Hi Marco,
I agree and I didn't want to rant. I just consider robustness and I
can not rely on or guarantee that cygwin kill ist used. (It is the
user of the Windows machine being creative ;-)
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?!
Greetings 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 13:00 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
2014-12-23 13:00 ` - [this message]
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=CAMhmPJ1xDjhepMTO3x2_AF6xo5mA3i193qKXJ5znfax7_YDDCg@mail.gmail.com \
--to=lopiuh@googlemail.com \
--cc=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=marco@gmail.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).