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=s9M6jV1gahGjng5v
	bHbe5qtYU7b3KSYN5z+akbmT33GzKtVvgLGRHEMm3losm92+pgAAGlFXWmv2hMtD
	3XkEdFQIjOT6O96/fVkxOZNMWeTnIZ51QJ1VrRUyYVfrq0+vGwpJ0t+h7ajsND4G
	EXEj7Zk/n3+V8W2+k4WrQV3fCJc=
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=ED4ej/BB3248d30jLyha1B
	voc5c=; b=Zp0jhD0CY93oe/tw218oFj9HrAht82+qhUDWxLVlxPebFJSPtc72BG
	mZTN5t6qhUfehFJujfspFMr/9O8e5eRIHjJk3CzWth3bulpM8J7ggjfNJextH5MR
	ZkxghABaXSlURb5liNezQLOs0X4MRRU/1o20RLJwA0QOXJZM74DXg=
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*UA:Bat!, H*x:Bat!, H*RU:192.168.1.10
X-HELO: forward103j.mail.yandex.net
Authentication-Results: smtp1j.mail.yandex.net; dkim=pass header.i=@yandex.ru
Date: Mon, 19 Mar 2018 05:56:09 +0300
From: Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To: cygwin AT cygwin DOT com
Message-ID: <774778050.20180319055609@yandex.ru>
To: Tatsuro MATSUOKA <matsuoka AT nuce DOT nagoya-u DOT ac DOT jp>, cygwin AT cygwin DOT com
Subject: Re: output waring for cygwin process running at setup__.exe
In-Reply-To: <11025.1286.qm@web103117.mail.kks.yahoo.co.jp>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id w2J35G1J025469

Greetings, Tatsuro MATSUOKA!

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


-- 
With best regards,
Andrey Repin
Monday, March 19, 2018 05:54:33

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