X-Recipient: archive-cygwin@delorie.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:from:to:references:in-reply-to:subject:date
	:message-id:mime-version:content-type:content-transfer-encoding;
	 q=dns; s=default; b=jggJWXfSaaQo0gUdSW8/HC/sR7fOYtPngEmY3Xf/p/Q
	o9irpQmTpQEu19HCNzXRlyHLzAV8NkH/pyLY+3PzXLk/CoIdo8P41zIgR0q+kTRt
	Teee+YjMgXa7ClPpnZVrP48YY3N7PDFArOrGxZu02oODXMw5EJJlRooJ7Osp/ESY
	=
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:from:to:references:in-reply-to:subject:date
	:message-id:mime-version:content-type:content-transfer-encoding;
	 s=default; bh=rnxYEkPlAXrghElaE5q45KrxYrE=; b=t8NS0diElVi7n6Kar
	HIIDG6y5IyVep5SR9wWfUiaR2N4c3WLC763eBnJTFYhxLv9CXy04M480XNAiAeJs
	w3SY71mzuVix/s+cD8yL0CRAbc842/cUcj6lVkRI6V+WFmWi/8YWIbKgk+KZSstY
	JFp2RmlzS/Fvym39i6ttCsgA/E=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mail-ig0-f180.google.com
X-Received: by 10.107.129.80 with SMTP id c77mr26488070iod.92.1419364067430;        Tue, 23 Dec 2014 11:47:47 -0800 (PST)
From: "cyg Simple" <cygsimple@gmail.com>
To: <cygwin@cygwin.com>
References: <CAMhmPJ2RMoDhF0V=i4=TKtJ2bD_JeNOecUKzKN=0wR1PH8O-sQ@mail.gmail.com> <CAMhmPJ1xDjhepMTO3x2_AF6xo5mA3i193qKXJ5znfax7_YDDCg@mail.gmail.com>
In-Reply-To: <CAMhmPJ1xDjhepMTO3x2_AF6xo5mA3i193qKXJ5znfax7_YDDCg@mail.gmail.com>
Subject: RE: Exitcode is 0 when killing a cygwin initiated process via taskmanager
Date: Tue, 23 Dec 2014 14:47:32 -0500
Message-ID: <01c701d01ee9$516e22d0$f44a6870$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;	charset="UTF-8"
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id sBNJm65A001755

> 
> 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?!

Cygwin is a POSIX environment executing within the Windows OS environment.  If things happen outside of the Cygwin environment it cannot  detect those.  You must train your users to not use the Windows Task Manager to kill the process outside of the Cygwin environment.

The problem does not exist in Linux because there isn't an environment inside an environment so there isn't a chance to use the tools improperly.

--
cyg Simple


--
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


