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:reply-to:subject:references:from:to:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=Xe3nnbHY9hE/og+r
	p/3u/vba2/HA4p2Pt23pb9YZzdwZoD9P6cmx1VFjragwi0Kwyc0RgfmBQKv/Ds5n
	ki85oAdRsDErOvg40piYNtRndzfe3Ww0TMPsi1UrHhMfBDiOfMav0kumQP22566b
	PCZ8nESGV5m55uyVX876QLWs3rw=
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:reply-to:subject:references:from:to:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=xhFxyHSsm/xevtBQYzghrv
	HN2eY=; b=Ds3QutAghKR5vF4JWKw8K2jbhF5DINBA64/oS8o4rZyhblgNnijpXr
	Zi70n83kyZzQEeDVjR7QjHComdYeP5XrRSUMOW8aglwg4aa9ONQxh3YEFnGhvMA5
	RX9rdB2oWgdfdghwyOm5jdbTk+WGBzu3MEp8pjICW93yswIWjawvM=
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.8 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=H*RU:!192.168.1.100!, H*r:ip*192.168.1.100, Hx-spam-relays-external:!192.168.1.100!, Menu
X-HELO:	smtp-out-no.shaw.ca
X-Authority-Analysis:	v=2.3 cv=X6B81lbe c=1 sm=1 tr=0 a=MVEHjbUiAHxQW0jfcDq5EA==:117 a=MVEHjbUiAHxQW0jfcDq5EA==:17 a=IkcTkHD0fZMA:10 a=fpAOSEmNAAAA:8 a=hfRR6VEHoO7IVqAC13kA:9 a=QEXdDO2ut3YA:10
Reply-To:	Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Subject:	Re: output warning for cygwin process running at setup__.exe
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> <1694481348 DOT 20180319070236 AT yandex DOT ru> <687282 DOT 15682 DOT qm AT web103112 DOT mail DOT kks DOT yahoo DOT co DOT jp>
From:	Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
To:	cygwin AT cygwin DOT com
Message-ID:	<daf01074-46f8-3680-0f24-28f950d8af4a@SystematicSw.ab.ca>
Date:	Sun, 18 Mar 2018 23:35:53 -0600
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version:	1.0
In-Reply-To:	<687282.15682.qm@web103112.mail.kks.yahoo.co.jp>
X-CMAE-Envelope:	MS4wfCW6RPeUMnp1U9jxOIcuVZBh4MOPxxdQvF4XFdkoP279IaIrHU6GRSNrKyqqYqMuwxtHOLFqnXejeAFvgdopBnlmZ4xwzsY9y3qQk/IQrsn+v/8iIwgu 93ab73zRxRfCMRjat7dmTncpj79nWaGFivPDWd7aS8m/WyKLe7uXPwDD1SqIZ2Irj5r7tmwAs2G56A==
X-IsSubscribed:	yes

On 2018-03-18 22:56, Tatsuro MATSUOKA wrote:
>  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. According to
>>>>> http://cygwin.wikia.com/wiki/Rebaseall, we have to kill or stop
>>>>> cygwin processes and services 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.

Cygwin setup uses standard Windows wininit processing to perform the
replacements on restart.

> Server service like cygserver always start after windows re-start if it is
> registered. So restart does not always kill cygwin processes. I do not want
> to force to  kill cygwin process by setupXX.exe but output the warning.
Only if a service is registered for Automatic startup: you can change this to
Manual, and restart services in a permanent last postinstall script prefix e.g.
zp_zzz_services.dash, which can also be executed by a scheduled task, before
starting Cygwin from e.g. a XWin Server taskbar or Start Menu shortcut.

Cygwin setup could operate more consistently and transparently if setup warned,
then shutdown running Cygwin services and noted them, and killed all remaining
processes, before beginning the install phase, then restarted previously noted
running services after the postinstall phase.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

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