Message-ID: <4D62843F.2000205@cornell.edu>
Date: Mon, 21 Feb 2011 10:26:55 -0500
From: Ken Brown <kbrown@cornell.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Spurious "Connection reset by peer" problems anybody?
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>
In-Reply-To: <20110221150636.GF17868@calimero.vinschen.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 2/21/2011 10:06 AM, Corinna Vinschen wrote:
> On Feb 21 09:54, Ken Brown wrote:
>> On 2/21/2011 9:26 AM, Corinna Vinschen wrote:
>>> On Feb 21 15:01, Corinna Vinschen wrote:
>>>> I spoke too soon. [...]
>>>
>>> Er... btw., is the situation something which is local to your
>>> environment or is it something which can be easily reproduced?
>>
>> The short answer is that it wouldn't be easy.  Here are the details:
>>
>> I keep a local mirror of the emacs bzr repository.  I connect to the
>> repository via bzr+ssh.  Every few days I refresh my mirror with
>> 'bzr up'.  When I do this from work, where I have a fast ethernet
>> connection, there's no problem.  When I do it from home, where I
>> connect to the internet via a wireless router, it often fails with
>> the "Software caused connection abort" message.  I keep retrying and
>> eventually it works. Sometimes it takes 10 tries, other times it
>> works on the first try.
>>
>> I've had similar problems in the past when using rsync to maintain a
>> local mirror of the texlive repository.  In that case I think the
>> error message was always "Connection reset by peer".  Once again,
>> the problem only occurred when working from home.
>>
>> I've always assumed that there was some issue with my home network
>> setup or my ISP, but I had no idea how to track it down.  It never
>> occurred to me that it could be a Cygwin/Windows problem.
>
> The problem is that this is not necessarily a Cygwin/Windows problem.
> It's just possible that Windows plays a role here.
>
> 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.

Ken

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