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:message-id:references:date:from:reply-to
	:subject:to:in-reply-to:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=rfAFN0FP7E2s1ZTn
	eleoB1I5l0zoziOGkqoVqrfe90vRbSaHMvjrWb+0nVTSa0+fApZJ4cnZazOD853x
	h1dBcQ0H8jfV3VGNVIkm7R8wd8Bt444o1M/a3ho3Ba7q+3BdpMKzdmfplQEk8kdr
	HdkDtR+4eFIvCGcyBa5u9ydWm6k=
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:message-id:references:date:from:reply-to
	:subject:to:in-reply-to:mime-version:content-type
	:content-transfer-encoding; s=default; bh=vVdE0RHfq9uOgUdJiPjQKW
	BqjgY=; b=RbAQv9jZJgI+J4ZAUrzSI+pFDyPULqldsJ6H2VVM1Bxicl5lssBbOj
	nI0QE9NYZz5FosicHHeFF2sdhu++m9vxIyaYdqDTxY32hzvtYcLLzFFg2J6Gwr6G
	vTcj3bIKqx0Ut13gR8N3bcmLK0h1Ax/1bQcDivY5/CD9D78Crxq7U=
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=-6.1 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,GIT_PATCH_2,RCVD_IN_DNSWL_NONE,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=H*M:yahoo, H*F:D*co.jp
X-HELO:	nh602-vm3.bullet.mail.ssk.yahoo.co.jp
Message-ID:	<687282.15682.qm@web103112.mail.kks.yahoo.co.jp>
X-YMail-JAS:	rFgI_AcVM1nvmY_lyDzgEMevJZTU.oltpqdZtZi5LeHJ4T.N48H4AO_CwLw8Hq168P4H0OxyZc3er4okd2c6FOU2CxHEPACtGnw8PSVpxTlgPC1uVT7QS0tCx42kwCbdOv4C
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>
Date:	Mon, 19 Mar 2018 13:56:19 +0900 (JST)
From:	Tatsuro MATSUOKA <tmacchant2 AT yahoo DOT co DOT jp>
Reply-To:	Tatsuro MATSUOKA <matsuoka AT nuce DOT nagoya-u DOT ac DOT jp>
Subject:	Re: output warning for cygwin process running at setup__.exe
To:	cygwin AT cygwin DOT com, Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
In-Reply-To:	<1694481348.20180319070236@yandex.ru>
MIME-Version:	1.0
X-IsSubscribed:	yes
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id w2J4uarZ002903

----- Original Message -----

> From: Andrey Repin 
> To: Brian Inglis ; cygwin
> Cc: 
> Date: 2018/3/19, Mon 13:02
> Subject: Re: output warning for cygwin process running at setup__.exe
> 
>G reetings, 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.
>
Sever survice like cygsever 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.
Tatsuro
Tatsuro

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