X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=Al
	ra2K2ZK/WUNB7wuwWbdVfMETneIu/KB2aeR0M9KDA4hyrfQjn2UQZ2JpKIp+7K/z
	3rvDy7SRi8OfQhwpyguNbirEprCH/ENiR02GAe1uqL557JmpgOV5jIb/0w3BbtQY
	ihHE//Hx3Z1Jv+PVlQ7i5bCvFnusqMWCuBmeerJzs=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; s=default; bh=ejlyEyK/
	kgqOe0ryKKTnbOam14I=; b=J2xl1kShthMX/SRgGSprzuQtuZ51T77hmH0hcTOo
	elz0G5OmKDQ8HJTDiAv09tAay6TTYImrh68ymXrllcG2Xc2lbovuIPg8HFikiZDL
	AV+oTNgNIUsMbNQAYBud1RzJpv+15XPQjBtpzijjCwUOud2eqH/rXjBlFnqEYEFT
	b44=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-2.0 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	mail-vc0-f178.google.com
MIME-Version:	1.0
X-Received:	by 10.52.242.199 with SMTP id ws7mr8346462vdc.75.1419339633915; Tue, 23 Dec 2014 05:00:33 -0800 (PST)
In-Reply-To:	<CAMhmPJ2RMoDhF0V=i4=TKtJ2bD_JeNOecUKzKN=0wR1PH8O-sQ@mail.gmail.com>
References:	<CAMhmPJ2RMoDhF0V=i4=TKtJ2bD_JeNOecUKzKN=0wR1PH8O-sQ AT mail DOT gmail DOT com>
Date:	Tue, 23 Dec 2014 14:00:33 +0100
Message-ID:	<CAMhmPJ1xDjhepMTO3x2_AF6xo5mA3i193qKXJ5znfax7_YDDCg@mail.gmail.com>
Subject:	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>

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

- Raw text -