From: Andrey Repin <anrdaemon@yandex.ru>
To: "Mainz, Roland" <Roland.Mainz@rovema.de>, cygwin@cygwin.com
Subject: Re: setup-x86_64.exe (bug ?): Cannot write to /usr/bin/cygwin1.dll - cyserver squatting it...
Date: Wed, 15 Nov 2023 20:01:44 +0300 [thread overview]
Message-ID: <1594716181.20231115200144@yandex.ru> (raw)
In-Reply-To: <DBBPR05MB111779EE12E855BE19BFE167B92B1A@DBBPR05MB11177.eurprd05.prod.outlook.com>
Greetings, Mainz, Roland!
> Hi!
> ----
> The Cygwin installer "setup-x86_64.exe" has problems updating cygwin1.dll when cygserver is running:
You should stop ALL Cygwin processes before starting setup.exe.
This is documented.
> ---- snip ----
> Unable to extract /usr/bin/cygwin1.dll -- error writing file
> ---- snip ----
> The fix is to do a $ sc stop cygserver # as Administrator, then
> "setup-x86_64.exe" can write to that file, and after "setup" is done do a $ sc start cygserverr # as Admin again.
> ... is it possible to modify "setup-x86_64.exe" to stop cygserver before
> doing the installation process and re-start it after it ?
There's no reason to do so, as there's no easy way to detect beforehand, if
you actually need to do so.
You could have cygserver running from one Cygwin setup but installing to the
different one. And so on.
--
With best regards,
Andrey Repin
Wednesday, November 15, 2023 19:59:00
Sorry for my terrible english...
next prev parent reply other threads:[~2023-11-15 17:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a0f1e420-ae48-49a3-9300-c56f1948ad9b.8d485f54-9f47-42b0-bdcb-9635fbf663c3.331c6002-7ca1-4c59-9494-402e573a76ee@emailsignatures365.codetwo.com>
[not found] ` <a0f1e420-ae48-49a3-9300-c56f1948ad9b.e52b7f5f-5a09-4346-99f8-a6591191169c.d8646e54-e135-4b48-b201-e04c766db67c@emailsignatures365.codetwo.com>
2023-11-15 13:57 ` Mainz, Roland
2023-11-15 17:01 ` Andrey Repin [this message]
2023-11-16 7:03 ` Martin Wege
2023-11-16 7:50 ` Brian Inglis
2023-11-16 15:50 ` Bill Sharp
2023-11-19 22:04 ` Jon Turney
2023-11-19 22:03 ` Jon Turney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1594716181.20231115200144@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=Roland.Mainz@rovema.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).