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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=Iu3kBc4UcXBWhG+tnky6dMzPZGAKAR2vO7RTXUYxRTF
	twY3gS9MQ/AKU43u5Wnpj302OJLuRTKZlutRYRdQxaR7mMYmrlLUpjOuNIemhMUa
	HL7fOqKLvL9RzWUhK/KOxMM5tm+3o4edUalHP2lXLrUeCwLJZQph/OruKdfnAgno
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=RkKPRgG7R2u6HAm5c6Zj0Mv6rd4=; b=jIbEp0G/Ad709CL9u
	1iHFNHDNaYdi27CrAeik8g34I1V3YESHtyHe/hYCJFsUUEIlqTNkesQzpnjj1MqA
	MGXzp/WcFOIpY5qxSW66ABMxOpVHLksfYYBDtYRldqfFZ8HYF33IAS/8omp3fpOa
	XhBp1I4Z+M7H1piXJHZthBhopo=
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.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mail-wg0-f48.google.com
X-Received: by 10.180.83.228 with SMTP id t4mr41016188wiy.28.1419334617046;        Tue, 23 Dec 2014 03:36:57 -0800 (PST)
Message-ID: <549953CC.9030903@gmail.com>
Date: Tue, 23 Dec 2014 12:36:44 +0100
From: Marco Atzeri <marco DOT atzeri AT gmail DOT com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Exitcode is 0 when killing a cygwin initiated process via taskmanager
References: <CAMhmPJ2RMoDhF0V=i4=TKtJ2bD_JeNOecUKzKN=0wR1PH8O-sQ AT mail DOT gmail DOT com>
In-Reply-To: <CAMhmPJ2RMoDhF0V=i4=TKtJ2bD_JeNOecUKzKN=0wR1PH8O-sQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-IsSubscribed: yes

On 12/23/2014 12:09 PM, - wrote:
>>> Using Taskmanager is brute force as cygwin dll can not act and correctly manage the exitcode
>
>
> Hi,
>
> thanks, but I do not agree. One element of the script was killed, not
> the hoöe script.

It was not killed in the proper cygwin way.

 > It should be more robust. What I do now is: Read
> stdout of the program (rsync) and only if I got the right footer of
> rsync I rely on exitcode 0.
>
> That is insane.

your opinion.

For me, it is simple: if you want a Unix like behavior use cygwin kill.

Otherwise propose a patch...
https://cygwin.com/acronyms/#PTC


> Is it possible to kill the process of a script element in GNU and
> having a returncode of 0 and a continuing script? If yes we can't use
> returncodes at all anymore in shell scripts?
>
> Thanks 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