X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DBFAF3854141 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1657527452; bh=UwIJmw6RVmpZH0BkAPB9VLws3GiJm33U0GHNZe8Sn8Y=; 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=QtaEnCGmuuKT+JFVkxnnfJ2ElxMPCxVGWNZFxLeYBsgMUY8F9dCJLfSsSfjmBFmtL H8aRTIRz3XwJnPqxoTziQ/1BOTjd4FwFyL7uaWOpFm9FUwY4tmMcvnN5q6Z05rwqiq 3ZUcsAweCo902UVK52hjz1RWGZw+sRIYOIj+pRdw= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org A13F338582A2 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 10:16:16 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: [EXTERNAL] Re: Spurious / persistent "exception" condition in half-closed sockets Message-ID: Mail-Followup-To: cygwin AT cygwin DOT com References: <649314d9-4862-af2d-3717-2809b818a820 AT cornell DOT edu> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-Provags-ID: V03:K1:O28NLMW1H5sFDzDP8xfIWGz+HJjkOoKyWyZ6zEpsW4XrgIjbFb2 2KEvf7R7pUbVKcoEuPfeBc7l2bIKnVhKPtf02ftbxYSldF4cgfxScd4My/NiBZqTYSDPDx6 Ht1MTRvLvmja7X0PB7eWlPDRIcLK+j5RSNsaZ7NPTWAeXGciUOPLMNPuV5TTisigxVmOFqX 8AEZMY5RjfGis1ROw6Ikw== X-UI-Out-Filterresults: notjunk:1;V03:K0:saZPEF52MtU=:Udg2fQaNv5da5NuIOO7Y6O gYLLEvjdOUL++gCexFqojfY3rrJI4MVBKUvbDc05fNMYWPj4mrX+m1zOAbzloe06m5lc5qicJ Ncq9wW84Pq6NQU8d4PVS3PqqcZLToPYHtkWOXWouF3c3Dq0DXl50j6FHig3Ik5dTAyu0/VTwv on0FuVgyprb3EqSKuCTN1DR1y6yJkrqjo+f8PhCt1shjPOn0XTpbte5UU6SEHbUtxcwdtKcSs InTjkREHSpQjiifJi57DrL/mCjstaEoehhA2dZGYVtq1YDXWjoI77M4UaoebIB6yNj2Q4HD4J sfluo1qGk4JlndVURbLUHXvKUasn700iYbEN5EOeLM9rLqB1gq5bsN6/Qg1ztqGbZXDjMWkQQ 6fFztMervy4rYBzysOW9DLN83ui9nlp1MT/4ZrNH6kYzFgvZyxeekF9hWPa2vllboQh1zD/Uz XGBXgzRroYa/GMjhfwCtxYlLsh/CdW4DF1Jq99lh1+4IX3I0Ud9G0SuDtw8uQsw8EMK/zzXGs yInvOjGuvOVMhXOjaJ5F0iiXUxrcPAVBCfCKPs+RoXN02YxVRrOQ591++xJlh5Z3lPqNlw2Ig nulLAAmMTuRpTZj85tCMkeeHex09HrSZc6yMG/oJndOk2KDl7uNlnCkDEYmDZ8hymXJztrTvJ yhg2IFKE6MADHYx5aSyU9YYYOdirLZkPvluA1nF8fPZhqqDcW4KGbaKP3bHZJdzS7O8vsOktP uhuuVUOZnBkflrhDM83QuqXnoSyOYqv4ZKWimmkCd0nNY+5RhgneJmU8GAw= 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 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: cygwin AT cygwin DOT com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" 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 -- 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