DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 12A2F385828E
MIME-Version: 1.0
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>
In-Reply-To: <c3fcf584-4d1f-4115-a861-272232248927@Shaw.ca>
Date: Thu, 16 Nov 2023 15:50:34 +0000
Message-ID: <CAH+C0MCgWoj67vQUvfggZ3TRU3Q7S=cG6M9FmTFJGAovy2FWBA@mail.gmail.com>
Subject: Re: setup-x86_64.exe (bug ?): Cannot write to /usr/bin/cygwin1.dll -
 cyserver squatting it...
To: cygwin AT cygwin DOT com
From: Bill Sharp via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Bill Sharp <bill DOT sharp AT gmail DOT com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

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.

Kind regards

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