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=dQoSCb0ZaRAe4jMw
	CIXtWxlkskMcErWSNjI/Fqg5DpHVEQcL9L2DBrN+O56Bk6MvalsIsNL7lmnajIqE
	FwxaVQURfBOex4057Z83eHebFH8Yoaj3dc/2A4OropzYYBAcAyQC9k5JOqaYWbQV
	D3hEoSuFSXMv6GiGduzqwkedYDU=
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=OZhPyGXJiaAJ8C1UBOe89M
	OXSbM=; b=pAOvoMKuXUZD761y/v0BhG8SAuWDdJuyPmEySNwFNeBhUv2wlIpVZN
	aQIQuFktlKWzvIOFwPZKNNY/57a17+buhJ+WM1VmWDjd4K4zIH0xbVBse0keRPmq
	RUeZgG1I+f/nzjlD1BCrnmw0Q43QY/K33PvBF3IXT/QCYXXYHCIq4=
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=inadequate, HTo:D*jp, H*Ad:D*jp, H*M:yahoo
X-HELO:	nh504-vm6.bullet.mail.kks.yahoo.co.jp
Message-ID:	<11025.1286.qm@web103117.mail.kks.yahoo.co.jp>
X-YMail-JAS:	GmLPg00VM1kEDyePOp1epu47Fh9XcHUugp9PQBVMHdQny5jhNQ_ZhaS.JWeBCbOSQ7ZWUpX8qsPL9iIUpSYiPKZ38s66m6cY_d_n4ys2yQWh6IifQBvg9XbGxBqrUxbR9Oab
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>
Date:	Mon, 19 Mar 2018 09:09:26 +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 waring for cygwin process running at setup__.exe
To:	cygwin AT cygwin DOT com, matsuoka AT nuce DOT nagoya-u DOT ac DOT jp
In-Reply-To:	<9410201895.20180319024642@yandex.ru>
MIME-Version:	1.0
X-IsSubscribed:	yes
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id w2J09fHB013211

----- Original Message -----
> From: Andrey Repin 
> To: Tatsuro MATSUOK cygwin
> Cc: 
> Date: 2018/3/19, Mon 08:46
> Subject: Re: output waring for cygwin process running at setup__.exe
> 
>G reetings, 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.
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 -