From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18608 invoked by alias); 22 Feb 2011 15:55:06 -0000 Received: (qmail 18146 invoked by uid 22791); 22 Feb 2011 15:54:41 -0000 X-Spam-Check-By: sourceware.org Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.83/v0.83-20-g38e4449) with ESMTP; Tue, 22 Feb 2011 15:54:34 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 9CEC62C02E1; Tue, 22 Feb 2011 16:54:30 +0100 (CET) Date: Tue, 22 Feb 2011 15:55:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Spurious "Connection reset by peer" problems anybody? Message-ID: <20110222155430.GH12399@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20110221104352.GA17868@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2011-02/txt/msg00487.txt.bz2 On Feb 22 10:40, Mirko Vukovic wrote: > On Mon, Feb 21, 2011 at 5:43 AM, Corinna Vinschen wrote: > > Hi listies, > > > > > > over the weekend I came across a description of a Windows socket problem > > which might affect some of us.  Fortunately I also came across the > > potential solution. > > > > My question is, does anybody have a scenario in which he or she > > encounters weird "Connection reset by peer" or "Software caused > > connection abort" messages in Cygwin, possibly at the end of a > > connection attempt? > > I have a problem on one of my machines when I try to do a git > push/pull to an external repo: > > > git push > Read from socket failed: Connection reset by peer > fatal: The remote end hung up unexpectedly > > I am not sure if that qualifies as a good test setup for you. Sorry, no. If that's git over ssh, it should be covered by a patch in the last developer snapshots. If it's occuring in the middle of a connection, rather than at the end, it's something else, not necessarily related to Cygwin at all. And, last but not least, given that the potential fix for the potential problem I talked about is definitely not feasible for Cygwin due to it's unsatisfying behaviour on dup'ed sockets, my request for a test has been entirely moot anyway. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple