X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Tue, 22 Feb 2011 09:54:46 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Spurious "Connection reset by peer" problems anybody? Message-ID: <20110222085446.GD12399@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20110221104352.GA17868@calimero.vinschen.de> <4D626D65.3060408@cornell.edu> <20110221140140.GD17868@calimero.vinschen.de> <20110221142606.GE17868@calimero.vinschen.de> <4D627C96.8000807@cornell.edu> <20110221150636.GF17868@calimero.vinschen.de> <4D62843F.2000205@cornell.edu> <20110221153406.GA11901@calimero.vinschen.de> <4D62E236.8000605@cornell.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <4D62E236.8000605@cornell.edu> User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Feb 21 17:07, Ken Brown wrote: > On 2/21/2011 10:34 AM, Corinna Vinschen wrote: > >On Feb 21 10:26, Ken Brown wrote: > >>On 2/21/2011 10:06 AM, Corinna Vinschen wrote: > >>>As far as this problem goes, it would only occur at the end of a > >>>connection, when close() is called on the socket on the Windows side. > >>>The error message would occur on the peer side, independent of the OS > >>>it's running on. If the connection just breaks at some arbitary point, > >>>it's almost surely not the problem I'm talking about. > >> > >>In my case the connection does break at some point in the middle, > >>not at the end, so it sounds like I have a different problem. > > > >Given that this is a bzr+ssh scenario, there's a good chance that your > >problem is fixed by the patch cgf applied tonight. Would you mind to > >test this with the latest snapshot? > > The problem is not fixed, but I think it's happening less often. (I > can't be sure, since the problem is sporadic.) Here's what I did: In that case your problem is very likely not related to what the patch fixes. Otherwise you would have seen either no problem at all, or, in the worst case, bzr+ssh hanging for a short while before finishing its job. 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