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:date:from:to:subject:message-id:mime-version
	:content-type; q=dns; s=default; b=psThQB7lNUifLizejvcAZci0inCaI
	onVcuZpNo+njLsx90bkroyzVgHxXvzaDubJRHwDojoJv1DP6voSQrw6ymoiGob6B
	M925EDLLTRcbeTa/tQYIyOvm+PjU4Cg3Di1Km2dPVsZs4qw6hLTAFd/cMNoBxetA
	y6+ujlxTUopT4s=
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:date:from:to:subject:message-id:mime-version
	:content-type; s=default; bh=WbXEaZZr80arnMtEznToXVdDUNE=; b=LAH
	8aEi0vD4fwrqyLPn3fx6FvnroPXyVsGQYFAdwpj6EeDg+WJ5ZWwjMZbME33kWez8
	6RGJCHKPKfT3nppK/liiNg9GQkwLCMarkitU67UPB928A+Ko8RBk92UOugbgb9+l
	/VufsxmSk+hjIJK4b73UfaaCzMkRkwlNg7sGiZ+M=
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.6 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=universitaet, Universitaet, damaged, tik
X-HELO:	smtp02.belwue.de
Date:	Thu, 19 Apr 2018 18:31:28 +0200
From:	Ulli Horlacher <framstag AT rus DOT uni-stuttgart DOT de>
To:	cygwin AT cygwin DOT com
Subject:	"setup-x86 --quiet-mode" problems
Message-ID:	<20180419163128.GA7093@rus.uni-stuttgart.de>
Mail-Followup-To:	cygwin AT cygwin DOT com
MIME-Version:	1.0
User-Agent:	Mutt/1.5.23 (2014-03-12)
X-IsSubscribed:	yes

I have an update script which calls "setup-x86 --quiet-mode".
So far, this works great, but now it tries to install a new mintty.exe,
but one mintty still running (where I started setup-x86), so setup-x86
kills this process... and setup-x86.exe is killed, too, which resulted in
a damaged cygwin installation :-(

I was able to fix it by running setup-x86.exe via Windows Explorer (puhhhh!).

How can I avoid this kind of problem in the future?

I tried it with:

setup-x86 --quiet-mode &
sleep 1
kill -9 $PPID

But setup-x86 was killed again, too.


-- 
Ullrich Horlacher              Server und Virtualisierung
Rechenzentrum TIK         
Universitaet Stuttgart         E-Mail: horlacher AT tik DOT uni-stuttgart DOT de
Allmandring 30a                Tel:    ++49-711-68565868
70569 Stuttgart (Germany)      WWW:    http://www.tik.uni-stuttgart.de/
REF:<20180419163128 DOT GA7093 AT rus DOT uni-stuttgart DOT de>

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

- Raw text -