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:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=N5bf5VmgDZR5qhG+
	MFk1hfLjQEe9EBZalQeXKfvFYTt78qmRp6dBkkOYfn1YkHe/UjbNFD0g8rkhCdvD
	ZzKTezVi2KHsrKWFXDQ9y7I8rskA7/x7xWYOnMTCIxD1X7artMoythxorKWF1L+z
	VK9twqS4HxeqOQmtwyx/MJmX1xM=
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:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; s=default; bh=RQgY8tbqjIR4wC2trQwMwl
	F/TgA=; b=tDyI1NU1hFSRGSIAEyUQysnyvxuu2CKb7wwvWm6n7wSxacCMCdTGQZ
	MdKqxz2yUaUOcJ3kfUS6uqf+2zIXGfJbQP7fIetDkBMhegdzobdJ8R4snv21uhq5
	lDoclf0x5fccSmNiZSysqweenSS4b0XmsmXVLWeowSIjHv0eevbNk=
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=-0.7 required=5.0 tests=BAYES_00,FREEMAIL_FROM,KAM_THEBAT,MIME_BASE64_BLANKS,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=no version=3.3.2 spammy=H*M:yandex, H*x:Bat!, H*UA:Bat!, H*RU:192.168.1.10
X-HELO: forward106o.mail.yandex.net
Authentication-Results: smtp1j.mail.yandex.net; dkim=pass header.i=@yandex.ru
Date: Mon, 19 Mar 2018 07:02:36 +0300
From: Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To: cygwin AT cygwin DOT com
Message-ID: <1694481348.20180319070236@yandex.ru>
To: Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>, cygwin AT cygwin DOT com
Subject: Re: output warning for cygwin process running at setup__.exe
In-Reply-To: <4afd0f8f-f3fd-d41f-1e82-2beb0804f109@SystematicSw.ab.ca>
References: <920600 DOT 51654 DOT qm AT web103111 DOT mail DOT kks DOT yahoo DOT co DOT jp>   <9410201895 DOT 20180319024642 AT yandex DOT ru>  <11025 DOT 1286 DOT qm AT web103117 DOT mail DOT kks DOT yahoo DOT co DOT jp>  <774778050 DOT 20180319055609 AT yandex DOT ru>  <4afd0f8f-f3fd-d41f-1e82-2beb0804f109 AT SystematicSw DOT ab DOT ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id w2J45HEq031666

Greetings, Brian Inglis!

> On 2018-03-18 20:56, Andrey Repin wrote:
>>>>> On cygwin setup, one has to kill cygwin process to execute autorebase 
>>>>> in the end of setup process. I think it is better to output warning at
>>>>> start stage setup if cygwin process running.

>>> Sorry for my inadequate description.
>>> At postinstall stage, cygwin setup execute
>>> /etc/postinstall/0p_000_autorebase.dash,
>>> this sometimes fails when Cygwin process(es) is(are) alive.
>>> Acooding to http://cygwin.wikia.com/wiki/Rebaseall,
>>> we have to kill or stop cygwin porcesses and sevices before rebase.
>>> This is why I propose that warning messages in pre-install stage in cygwin setup.
>> 
>> Sounds about right.
>> If there's an existing Cygwin install, it is possible to run ps.exe and see if
>> it find any running Cygwin processes before attempting an update.

> If there's not an existing Cygwin install, you don't really have to worry too
> much about Cygwin processes running. ;^>

Yes.

> The docs all recommend killing all Cygwin processes *before* running setup, as
> setup can not replace running exes and active dlls during the installation
> phase, before postinstall rebase of replaced dlls.

> If setup can not replace any exe or dll, it warns you have to restart your
> system to complete the replacement. After the restart, you then have to rerun
> setup with no Cygwin processes running to successfully rebase replaced dlls.

The problem is, not all packages are prepared to deal with locked shared
objects (in truth, none are).
Which may leave system in an inconsistent state even after reboot.


-- 
With best regards,
Andrey Repin
Monday, March 19, 2018 07:01:13

Sorry for my terrible english...
--
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