X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 8F0A73830752
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1700431496;
	bh=FPlEC3WDgdci2O4VBMfJM/9MP5VLOm2L53z29qFfq6E=;
	h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	From;
	b=P8oCKtin1I5+D9vlIN10nTW79fyhpP+2pGbHMeSWnd7I7z/lu2YGMlLixXiAmUH6+
	bKLq36glTbAbWLWzHriUTWLGVVGxlJl+CFSSKJ37e5GMxXufXo5dHdmgcfpwaaageK
	8rNb1w7RycdRJZHREyJW7ACE+1cH2FfvhLKTx3T8=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.2 sourceware.org 7E66A388883C
ARC-Filter:	OpenARC Filter v1.0.0 sourceware.org 7E66A388883C
ARC-Seal:	i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1700431472; cv=none;
	b=gMeXfOqiTOzpJpMVJulUhmU+Mbs1Du/YALDxT1kY1qJZH3PKdrYB41VZtegnD2rvFyszc9ZJbwswYBxOcQdG0MjMQGic8bxePmbM1VDugN8SSf0yoEMJHqD3SI9cvjarmQgxJ0gdjRqCbt5zU5ttkcg3eMO/khhGmnXjMDOd5og=
ARC-Message-Signature:	i=1; a=rsa-sha256; d=sourceware.org; s=key;
	t=1700431472; c=relaxed/simple;
	bh=6kS3V1EYUzHBtpiYs+8eGlgqNbyrOTOJmUCmuJKFEIw=;
	h=Message-ID:Date:MIME-Version:Subject:To:From;
	b=KP1+DwvNFtTjX+CR8sJy496XOPFdo9hYR22/N+rzdom9a4J+LwcZq0Dn5MjLIETIUr1o+sliok6dyYd5CuAFbbB2xbKT9IBd23pMEWNduhTHg0GDOadF98EZAlI98p5CQz6ZywyyGCTBX+bKYUBeGlDnyTi0EUAp3QW9uZH0KaY=
ARC-Authentication-Results:	i=1; server2.sourceware.org
X-SNCR-Rigid:	64C837300BB7311E
X-Originating-IP:	[81.153.98.243]
X-OWM-Source-IP:	81.153.98.243 (GB)
X-OWM-Env-Sender:	jon DOT turney AT dronecode DOT org DOT uk
X-VadeSecure-score:	verdict=clean score=0/300, class=clean
X-RazorGate-Vade:	gggruggvucftvghtrhhoucdtuddrgedvkedrudeggedgudehiecutefuodetggdotefrodftvfcurfhrohhfihhlvgemuceutffkvffkuffjvffgnffgvefqofdpqfgfvfenuceurghilhhouhhtmecufedtudenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepkfffgggfuffvfhfhjggtgfesthejredttddvjeenucfhrhhomheplfhonhcuvfhurhhnvgihuceojhhonhdrthhurhhnvgihsegurhhonhgvtghouggvrdhorhhgrdhukheqnecuggftrfgrthhtvghrnhepiefggeekgfelleelgeetuefgfeejtdeigedvheeuvdfhjeffgeetfedtkeejtdfhnecuffhomhgrihhnpegthihgfihinhdrtghomhenucfkphepkedurdduheefrdelkedrvdegfeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhephhgvlhhopegludelvddrudeikedruddruddtjegnpdhinhgvthepkedurdduheefrdelkedrvdegfedpmhgrihhlfhhrohhmpehjohhnrdhtuhhrnhgvhiesughrohhnvggtohguvgdrohhrghdruhhkpdhnsggprhgtphhtthhopedvpdhrtghpthhtohepsghilhhlrdhshhgrrhhpsehgmhgrihhlrdgtohhmpdhrtghpthhtoheptgihghifihhnsegthihgfihinhdrtghomhdprhgvvhfkrfephhhoshhtkeduqdduheefqdelkedqvdegfedrrhgrnhhgvgekuddqudehfedrsghttggvnhhtrhgrlhhplhhushdrtghomhdprghuthhhpghushgvrhepjhhonhhtuhhrnhgv
	hiessghtihhnthgvrhhnvghtrdgtohhmpdhgvghokffrpefiuedpoffvtefjohhsthepshgrqdhprhguqdhrghhouhhtqddttddu
X-RazorGate-Vade-Verdict:	clean 0
X-RazorGate-Vade-Classification:	clean
Message-ID:	<ab9afaa2-b939-4937-a220-636e49b8f274@dronecode.org.uk>
Date:	Sun, 19 Nov 2023 22:04:29 +0000
MIME-Version:	1.0
User-Agent:	Mozilla Thunderbird
Subject:	Re: setup-x86_64.exe (bug ?): Cannot write to /usr/bin/cygwin1.dll -
	cyserver squatting it...
To:	Bill Sharp <bill DOT sharp AT gmail DOT com>,
	The Cygwin Mailing List <cygwin AT cygwin DOT com>
References:	<a0f1e420-ae48-49a3-9300-c56f1948ad9b DOT 8d485f54-9f47-42b0-bdcb-9635fbf663c3 DOT 331c6002-7ca1-4c59-9494-402e573a76ee AT emailsignatures365 DOT codetwo DOT com>
	<a0f1e420-ae48-49a3-9300-c56f1948ad9b DOT e52b7f5f-5a09-4346-99f8-a6591191169c DOT d8646e54-e135-4b48-b201-e04c766db67c AT emailsignatures365 DOT codetwo DOT com>
	<DBBPR05MB111779EE12E855BE19BFE167B92B1A AT DBBPR05MB11177 DOT eurprd05 DOT prod DOT outlook DOT com>
	<1594716181 DOT 20231115200144 AT yandex DOT ru>
	<CANH4o6Ou6M13+gfA4zYvz_aseMDcc+q6v9HFjgXFNWgk8zYGVw AT mail DOT gmail DOT com>
	<c3fcf584-4d1f-4115-a861-272232248927 AT Shaw DOT ca>
	<CAH+C0MCgWoj67vQUvfggZ3TRU3Q7S=cG6M9FmTFJGAovy2FWBA AT mail DOT gmail DOT com>
In-Reply-To:	<CAH+C0MCgWoj67vQUvfggZ3TRU3Q7S=cG6M9FmTFJGAovy2FWBA@mail.gmail.com>
X-Spam-Status:	No, score=-2.3 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL,
	KAM_DMARC_STATUS, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H5, RCVD_IN_MSPIKE_WL,
	SPF_HELO_PASS, SPF_PASS, TXREP,
	T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6
X-Spam-Checker-Version:	SpamAssassin 3.4.6 (2021-04-09) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.30
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Jon Turney via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Jon Turney <jon DOT turney AT dronecode DOT org DOT uk>
Errors-To:	cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

On 16/11/2023 15:50, Bill Sharp via Cygwin wrote:
> On Thu, 16 Nov 2023 at 07:50, Brian Inglis via Cygwin <cygwin AT cygwin DOT com>
> wrote:
> 
>> On 2023-11-16 00:03, Martin Wege wrote:
>>> This is not helpful. Cygwin setup-x86-64.exe not being able to update,
>>> because SOMETHING is locking cygwin1.dll is in the top 50 of your IT
>>> support, right followed by the question of IT support whether
>>> "updating to WSL" will solve the situation for them permanently.
>>
>>
>> There may be critical or just really long Cygwin processes running that
>> should
>> not be killed because somebody wants to upgrade.
>>
>> Shutting down processes, including services, has to be left to the users
>> or sys
>> admins who understand whether the circumstances are suitable to kill
>> processes
>> to do an upgrade.
>>
> 
> 
> I actually agree with both of you to an extent.
> 
> However I would like to suggest the correct enchancement here would be for
> setup to check for any running cygwin processes and then barf a warning
> onto the user, referncing the appropriate documentation, before allowing
> them to proceed.

Well, what is supposed to happen at the moment (since [1]), for 
processes in the current user's session at least, is better than that - 
we check if a file we want to replace is actually in use by a Cygwin 
process and offer to terminate that for you.

If that isn't working, that would probably be a bug, and we'd like to 
hear about it.

[1] https://cygwin.com/pipermail/cygwin-apps/2013-February/031448.html


I realize this is all well-intentioned, but this discussion is not 
actually contributing very much.  As always, the difficulty in making 
this change is not working out what setup should do, but that someone 
has to do it.  (A situation unfortunately so common, we have an acronym 
for it: [2])

[2] https://cygwin.com/acronyms/#SHTDI


-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -