Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 10 Apr 2002 10:24:50 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: SSH -R problem Message-ID: <20020410102450.K1127@cygbert.vinschen.de> Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.22.1i On Tue, Apr 09, 2002 at 11:48:56PM -0400, Steve Chew wrote: > Everything works OK at first but after enough sessions are made > across the SSH tunnel, I can no longer open sockets and other network > programs on the Cygwin system (such as IE) fail. If I create enough > sessions the entire system can hang. > [...] > One symptom of the problem is that after each session > I end up with an extra socket in the LISTEN state on the Cygwin box > (use netstat -an to check the socket states). I don't know why there > would even be any sockets in the LISTEN state on the Cygwin box since > the ssh client shouldn't have to do a listen. I can reproduce it on XP. An strace output shows nothing strange. Especially listen() is never called (otherwise it would show up in strace). I must assume that this is one of several annoying problems in Winsock. I've no idea why a socket is going into LISTEN state under these circumstances. Baffled, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/