From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [EXTERNAL] Re: Spurious / persistent "exception" condition in half-closed sockets
Date: Mon, 11 Jul 2022 10:16:16 +0200 [thread overview]
Message-ID: <YsvcUCG4BqXQuZaQ@calimero.vinschen.de> (raw)
In-Reply-To: <YsvWvXoAd5U+41qF@calimero.vinschen.de>
On Jul 11 09:52, Corinna Vinschen wrote:
> On Jul 9 23:02, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
> > > This was fixed in Cygwin 3.3.0, as the announcement of the latter stated:
> >
> > Thanks! So maybe it is time to upgrade... after all LOL
> >
> > > But you can still run a parallel Cygwin installation
> >
> > I tried that before... And it did not work out well. Unless it's a VM,
> > there's a small but real chance that at some point they are to get intertwined,
>
> This must have been very long ago. For a long time, Cygwin's path
> handling and shared memory interaction between Cygwin processes is
> based on the installation path of the Cygwin DLL a process is running
> under. A Cygwin process running under a Cygwin DLL from path A uses
> different default Windows PATH and different shared memory names than a
make that "different names for all shared objects"
> process running under Cygwin DLL from path B. Keeping Cygwin
> installations separate just requires never to run processes from
> installation A under Cygwin DLL B.
>
>
> > and then ... it's quite a mess (learned that the hard way, unfortunately).
>
> It really isn't. Only if you start to mix paths from two parallel
> Cygwin installations inside the same shell session, which should be
> easy to avoid.
>
>
> Corinna
prev parent reply other threads:[~2022-07-11 8:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 15:37 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-07-09 21:05 ` Ken Brown
2022-07-09 23:02 ` [EXTERNAL] " Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-07-11 7:52 ` Corinna Vinschen
2022-07-11 8:16 ` Corinna Vinschen [this message]
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=YsvcUCG4BqXQuZaQ@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).