public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Vince Rice <vrice@solidrocksystems.com>
To: cygwin <cygwin@cygwin.com>
Subject: Re: "setup-x86 --quiet-mode" problems
Date: Thu, 19 Apr 2018 16:36:00 -0000	[thread overview]
Message-ID: <FBCCE6D8-916C-482C-A5AE-B97753596075@solidrocksystems.com> (raw)
In-Reply-To: <20180419163128.GA7093@rus.uni-stuttgart.de>

> 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

  reply	other threads:[~2018-04-19 16:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-19 16:31 Ulli Horlacher
2018-04-19 16:36 ` Vince Rice [this message]
2018-04-19 23:28 ` Brian Inglis
2018-04-20 10:23   ` Ulli Horlacher
2018-04-22 14:05     ` Andrey Repin
2018-04-22 16:28       ` Brian Inglis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=FBCCE6D8-916C-482C-A5AE-B97753596075@solidrocksystems.com \
    --to=vrice@solidrocksystems.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).