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:date:message-id:subject:from:to
	:content-type; q=dns; s=default; b=e08XUF7Z6umscRV7GBlkQ/7tHM1nU
	ip7Ir8vT+LmvuREwCsegyCuR4lS2MzCxaNQ0ZI+leOpfMiLNX7C8oy3qeNvf9ZoA
	+WbAtJ+8UVHrAkl+j4rFXGwzrggF8EXQ3XDpHbU20Xmlq5z1gDomPe9heC6lFkmq
	Wjyc6DLeRHVgUU=
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:date:message-id:subject:from:to
	:content-type; s=default; bh=fAD+eHj8azhC6iaPbE+LTR3r6zQ=; b=j6k
	u57FBpUR79O08lqZ2nlpii3S9yrcuRURIYs1JD5PU4tLD+sxgSodcKi7tiLfQ6kz
	Rs8KkeyDni93RDDTmlcgNvxhCIYm3KC0q4mZwo+e0dG+VIA5dX2C9u+rXSFLdFEp
	QIUgk03oWlBtHN0GyoU8pJGr7dUUgHSCeGkjePzA=
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=-1.4 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-f180.google.com
MIME-Version: 1.0
X-Received: by 10.220.74.197 with SMTP id v5mr9093557vcj.27.1419302037141; Mon, 22 Dec 2014 18:33:57 -0800 (PST)
Date: Tue, 23 Dec 2014 03:33:57 +0100
Message-ID: <CAMhmPJ1P12vuK1gXhL=25p5GbSGbahZGY+4co+bzUFG96iXK8g@mail.gmail.com>
Subject: Re: Exitcode is 0 when killing a cygwin initiated process via taskmanager
From: - <lopiuh AT googlemail DOT com>
To: cygwin AT cygwin DOT com, anrdaemon AT yandex DOT ru
Content-Type: text/plain; charset=UTF-8

Hi,

>> Any idea how to solve (get the "canceled" exit code? Remember: The
>> script continues like a normal finish of the command)

> What do you mean by "canceled" exit code, pretty please?

oh, any exitcode <> 0 would be nice. Sending sigkill on debian gives a 137.

The point is, I rely on having a successfully executed command, if
exitcode is 0. In this case command is terminated, left garbage and
did not do its job and I go on like everything would be fine. How
should error checking care about such a condition / state?

Any ideas? And by the way, is such a condition in pure GNU/Linux
producible? Sigkill is quite brute force exit isn't it?

Thanks

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