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:from:content-type:content-transfer-encoding :mime-version:subject:date:references:to:in-reply-to:message-id; q=dns; s=default; b=glChBh8jw6CTNm9IAohhOzEKye4mcYx1Xt163LppKHc czbZMIv35LAW2PznpV09tHUsV8bvFa3SvoOAsp1lajW2mzZqowavRIaMlCpX+mSa mHau8+3uwLSvKN2li0baTB3SI5Olx5YxwUSclyp6o6TurFhLujQ26AXzYmu7BDAY = 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:from:content-type:content-transfer-encoding :mime-version:subject:date:references:to:in-reply-to:message-id; s=default; bh=Y4D71wB22PiJ3S/ePIT3SkRa3pk=; b=rRdE0qx8K3nIqTGUd rkEVv4H6aNxYxnr9Ul6SsEqPrprtZlF/0+BVQu7PzksZrzDZkYIsqG0BY5Wm2ay5 RAA65EG6BHYtpSq8YfntrmFYmD8t5SZqOyfRCWFDFg9EwNhIv7RjKz4gdkd5XIRj /++pWO7+Jk3NmlRDTe8J12Fl1g= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=ulli, Ulli, Setup X-HELO: gproxy4-pub.mail.unifiedlayer.com X-Authority-Analysis: v=2.2 cv=M5g9E24s c=1 sm=1 tr=0 a=x/h8IXy5FZdipniTS+KQtQ==:117 a=x/h8IXy5FZdipniTS+KQtQ==:17 a=IkcTkHD0fZMA:10 a=Kd1tUaAdevIA:10 a=1qdAB5wHU9LYvQeR6gUA:9 a=QEXdDO2ut3YA:10 From: Vince Rice Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: "setup-x86 --quiet-mode" problems Date: Thu, 19 Apr 2018 11:36:10 -0500 References: <20180419163128 DOT GA7093 AT rus DOT uni-stuttgart DOT de> To: cygwin In-Reply-To: <20180419163128.GA7093@rus.uni-stuttgart.de> Message-Id: X-BWhitelist: no X-Exim-ID: 1f9CXb-003ILs-Ps X-Source-Sender: 99-106-192-34.lightspeed.ftwotx.sbcglobal.net ([192.168.1.64]) [99.106.192.34]:61989 X-Source-Auth: vrice AT solidrocksystems DOT com X-Email-Count: 1 X-Source-Cap: c29saWRycjI7c29saWRycjI7Ym94ODY3LmJsdWVob3N0LmNvbQ== X-Local-Domain: yes X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id w3JGaSKa015075 > On Apr 19, 2018, at 11:31 AM, Ulli Horlacher wrote: > > 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. The way you fixed it already — don't run setup under mintty (or dash or …). Setup is not a cygwin program (it's not linked to cygwin1.dll). It's safest to have all of your cygwin processes stopped when you run setup, anyway, to prevent problems just like this. -- 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