X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 359D3385829C
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1657525980;
	bh=Rk3QXF6IWeOs/iRrMQW17uHNMKCZ7jauglQoFRoqcgo=;
	h=Date:From:To:Subject:References:In-Reply-To:List-Id:
	List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe:
	Reply-To:From;
	b=RFm76nKD2yu74a9QgGXEnyB6aJTgze+h/pIKKaxEX+ogin1TVAs0PItuNuxE6RM4m
	MLFVzEYxDRfQ/ACGKRNf3oj0BEz+mydSgSRpF7goEuMQcwilao4A2Uk8bwRKaCUkrp
	KJ1g0aFoVe6I/1KXKS4ue4AUhPXoyaYAnWUPnBvU=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.1 sourceware.org 39D3B38582A2
Authentication-Results:	sourceware.org;
	dmarc=fail (p=none dis=none) header.from=cygwin.com
Authentication-Results:	sourceware.org; spf=fail smtp.mailfrom=cygwin.com
Date:	Mon, 11 Jul 2022 09:52:29 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: [EXTERNAL] Re: Spurious / persistent "exception" condition in
	half-closed sockets
Message-ID:	<YsvWvXoAd5U+41qF@calimero.vinschen.de>
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<DM8PR09MB7095465D639E6A96C5615E84A5859 AT DM8PR09MB7095 DOT namprd09 DOT prod DOT outlook DOT com>
	<649314d9-4862-af2d-3717-2809b818a820 AT cornell DOT edu>
	<DM8PR09MB709579155BA92F3E3A43039BA5859 AT DM8PR09MB7095 DOT namprd09 DOT prod DOT outlook DOT com>
MIME-Version:	1.0
In-Reply-To:	<DM8PR09MB709579155BA92F3E3A43039BA5859@DM8PR09MB7095.namprd09.prod.outlook.com>
X-Provags-ID:	V03:K1:0WzJNU7R2ZqErXfAUaGq66hcBFevP+W9VY7C9Sb+nLZDhL96HHd
	C0qS/18wnJ/AcCkjW5ck0wDIWZMd0hIs5yo+5rxYNqB8zafwRjaRCq8npQioYKL7bz2OgX9
	8HLYnmRQ0jVpiL80/gEqq7rn8u8rVKecUlu8Le4yMM2PjmoXuZkjI6KccFc7A6jZ12Q13hZ
	n99PbkPOrsVMw2kMBUyCQ==
X-UI-Out-Filterresults:	notjunk:1;V03:K0:k+s5flJa600=:WeH+2EwdHt5WvwiHcUOuOg
	Rf/OZwLTigmFk/Fb0b+Yuk7jyU6h8xiCHz6dngQ9jDsDcFRWsObkroKC4rzB1WM/CTJEqP0Pf
	E2H0gR4knFMHFnwrN2Pvlq7BBIA+xnAoE4pcJOENPJrIsDAYrZF+X0ADMy1R/JDtKISsi9dQ/
	K0zi3922V0v76xOcfoDTJYcLdrN+0M3sQrIlGt4ldsvuAhGG17bjh4LGxEtN1qxLVlEyyAwdL
	oTLHD7KR8SnA6Uj/jeYJqR/FjCFyElcQxfH2Tw3KWrSzTvjovqqJJ38Lm1SsjFs1HHWD6shfQ
	5sYva9I6+X9E39AQwmJL8mkqn8xLqJr6NeOwMRR8QsQn9ia00LzcqD1mC4gbga0tNIs13kpNz
	MznDEKGjSLYMDGrZwXtVCYVaNqrSTRKCJcCD22FB6akmXUhmZ1DoTqH68/6PTNucw1J+ol3q7
	ZkK9FM0mBN1wF14YWNHKZjdsrDQAiXd9YOljAfsXNxXDvrIbes8JYBkPtfpdhyTqUhc1/kE5y
	MrME73ohJlgVIkmv5cIxNuGkoZy/mHT5VvSwelt1ud1+KvjGQHMKxYzxXjR3plOPMj3/DUz6M
	95DGEJ/0/Vc2BJbt4Kf0lj4MudIawFVhXYPQSz6aObo72hAqItNUoxLyg/4xTbHYO76OMzLET
	4ctEdlMHoBZgO3OkAOQfQJmLbGY56r7BWo/X67WYYdnM1Jo/ZH2cBZ3u4mrcuEJOd4qzJDzFW
	Y38YBFadBS+N2cRYUQzcTUuOQOhYpj1gNsFQls5UvTyhMKt0zjQ3Q94a/1s=
X-Spam-Status:	No, score=-95.2 required=5.0 tests=BAYES_00,
	GOOD_FROM_CORINNA_CYGWIN, KAM_DMARC_NONE, KAM_DMARC_STATUS, RCVD_IN_DNSWL_NONE,
	RCVD_IN_MSPIKE_H2, SPF_FAIL, SPF_HELO_NONE, 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.29
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>
Reply-To:	cygwin AT cygwin DOT com
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 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
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

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