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=Gx
	weqLxh0cn05WntL2qTwSVJEup68Qa17u7uvMT1KzTpXYjxLMEtKbQy4nwEFXUfNd
	ZCi63OVkIui1H11ZqQLPDxZqvpKYt3ghbaQgOh2zyq6tGSes47vmkXEMEGX/D5HA
	VdyawpTcHdv5ONYIbX7EV6ePRNNXnyudrRoYIppsc=
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=brLSnFZj
	7gH3S1Z6s+q6cbgSMTE=; b=UGaBN6nnulcmy/JTJPo66PD0v37Tig1XTDtvbt5t
	c9X1S2sk77Jyo21PFrjaKM+fo/EsVs9niDPvct1dGXz0Vz0/ZnSVoIl3umlnTaqU
	LtviDu5sj0ySxIvd8hvOUgHYtnxMhu5Zxx+0wXvbwcSmw41kEjsqRwgoQYF7cteH
	YMk=
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.1 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-f177.google.com
MIME-Version: 1.0
X-Received: by 10.220.5.72 with SMTP id 8mr12215599vcu.6.1419386171450; Tue, 23 Dec 2014 17:56:11 -0800 (PST)
In-Reply-To: <CAMhmPJ1xDjhepMTO3x2_AF6xo5mA3i193qKXJ5znfax7_YDDCg@mail.gmail.com>
References: <CAMhmPJ2RMoDhF0V=i4=TKtJ2bD_JeNOecUKzKN=0wR1PH8O-sQ AT mail DOT gmail DOT com>	<CAMhmPJ1xDjhepMTO3x2_AF6xo5mA3i193qKXJ5znfax7_YDDCg AT mail DOT gmail DOT com>
Date: Wed, 24 Dec 2014 02:56:11 +0100
Message-ID: <CAMhmPJ1-RgCLqpUX95x6YJTkq=rEX7ZFiCDkKdBjDnXVt5xSdw@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>,
        cygsimple AT gmail DOT com
Content-Type: text/plain; charset=UTF-8

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

Ok I wrote a wrapper and check stdout of critical commands. If I get
returnvalue 0 but not expectet stdout I panic. As far as my critical
part is rsync that is a safe bet (there is a nice footer when rsync
was not interrupted).

As far as robustness is concerned I must say I am happy having found
this edge very early.

What do you think is that topic worth an entry in FAQ/Documentation?
On the other hand this thread will be found through google search...

Thanks again for being supportive and all your work!

lopiuh

keywords: cygwin returnvalue errorcode taskmanager exitcode process
kill end continue zero errorvalue unset

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