From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26298 invoked by alias); 23 Dec 2014 19:47:52 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 26283 invoked by uid 89); 23 Dec 2014 19:47:51 -0000 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 Received: from mail-ig0-f180.google.com (HELO mail-ig0-f180.google.com) (209.85.213.180) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Tue, 23 Dec 2014 19:47:49 +0000 Received: by mail-ig0-f180.google.com with SMTP id h15so6029650igd.1 for ; Tue, 23 Dec 2014 11:47:47 -0800 (PST) X-Received: by 10.107.129.80 with SMTP id c77mr26488070iod.92.1419364067430; Tue, 23 Dec 2014 11:47:47 -0800 (PST) Received: from eboyd53entlt1 (9.sub-70-208-200.myvzw.com. [70.208.200.9]) by mx.google.com with ESMTPSA id uw1sm6725629igb.19.2014.12.23.11.47.25 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 23 Dec 2014 11:47:46 -0800 (PST) From: "cyg Simple" To: References: In-Reply-To: Subject: RE: Exitcode is 0 when killing a cygwin initiated process via taskmanager Date: Tue, 23 Dec 2014 19:47:00 -0000 Message-ID: <01c701d01ee9$516e22d0$f44a6870$@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2014-12/txt/msg00350.txt.bz2 >=20 > I scratch my head if we have a similar situation in GNU/Linux. >=20 > If anything went havoc I so far supposed that exit code or abrupt script > breakdown (stop) cares about not doing nasty things. >=20 > 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 momen= t. Is > that true in GNU/Linux as well? What do you think? I can't find a clear = answer in > the www so far. >=20 > 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 th= e process outside of the Cygwin environment. The problem does not exist in Linux because there isn't an environment insi= de 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