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:to:message-id:in-reply-to:references
	:subject:mime-version:content-type:content-transfer-encoding; q=
	dns; s=default; b=fQHCm7WWcqtHJ9kC8YltBAPITFK72iBhN/7MVp1woG3WOc
	rmg2QrrHoTpGMClIOOQQGzEK73zfOc2rgmqcLYCOJuoKNRe958bsGsOyyFEwo9xs
	Kenk18nAmgGl5K0Uw/5P0i4s5ikw5bORKXOtNDouko37hX8U+Pgsn2obw3rJ8=
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:to:message-id:in-reply-to:references
	:subject:mime-version:content-type:content-transfer-encoding; s=
	default; bh=kGj1xZUQIW9ZNiKc5jiOogxUK7I=; b=WEB6qxZY8KnMZxOS7JLW
	a42/t8Kadroez9B+mim6QjaEnF+DHnk9RQur+MBA9mG/su40OoXx7ZUcl8bdAXzX
	ahJsmM+lFQRzrqZOwCzxqDmyUP2JJ4/L+Ke4lhKkVRrLtf6ed41UKzyGZuSfREBR
	A2liKoBT1vOsO2JPg2TuQyU=
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.1 required=5.0 tests=BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,SPF_HELO_PASS,SPF_SOFTFAIL,URI_HEX autolearn=no version=3.3.2 spammy=wish, H*F:D*co.jp
X-HELO: n5.nabble.com
Date: Sun, 18 Mar 2018 20:35:07 -0700 (MST)
From: Tatsuro MATSUOKA <tmacchant2 AT yahoo DOT co DOT jp>
To: cygwin AT cygwin DOT com
Message-ID: <1521430507584-0.post@n5.nabble.com>
In-Reply-To: <774778050.20180319055609@yandex.ru>
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>
Subject: Re: output waring for cygwin process running at setup__.exe
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

>>>>  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 worning at start stage setup if cygwin 
>>>>  process running. 
>>> 
>>> I'm not quite sure of the steps you took to come to such conclusion. 
>>> Can you please explain? 
>>> 
>>> 
>> 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. 

Thank for your vote.
I hope my wish will become reality.

Tatsuro

-- 
With best regards, 
Andrey Repin 



--
Sent from: http://cygwin.1069669.n5.nabble.com/Cygwin-list-f3.html

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