delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2003/02/14/14:58:42

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <FC0B9DA2600ED4118F76009027AA5DDD0485B366@ALEX2>
From: jeff_burch AT agilent DOT com
To: cygwin AT cygwin DOT com, Tino DOT Lange AT isg DOT de
Subject: RE: Problem with accept(2) on the 1003.20.0.0 release
Date: Fri, 14 Feb 2003 10:59:02 -0800
MIME-Version: 1.0
X-Spam-Status: No, hits=-97.6 required=5.0
X-Spam-Level:

Dear Tino and the rest of the Cygwin community,

I made a post yesterday (2/13) on this problem and posted a testAccept.cpp program. By the way, my new version of cygwin and g++ agreed perfectly with Tino's response. Also, tests to use a specific "real" address in the bind( ) call didn't change the  problem behavior...

As an experiment, I happened to have an old version of cygwin's install package on a server and have move the problem machine back to the distant past: 

uname -a
CYGWIN_NT-5.0 SSLGROUPOB 1.3.3(0.46/3/2) 2001-09-12 23:54 i686 unknown

g++ --version
2.95.3-5

The testAccept.exe built on this version of Cygwin works perfectly. Also, my testAccept.exe built on the lastest version of Cygwin runs perfectly on this version of Cygwin. And one more "fun fact": I tweaked the program and built it under Visual C++ and it runs perfectly.

So, on my machine the new version of Cygwin has a problem! Accept(2) will hang on the second call for the same socket. I wonder who else in the world will have similar problem. Tino reports that he doesn't have any problems on his machine...

At this point, I don't know what else to try. I'm pretty sure the problem is down in the new cygwin1.dll but I don't have the time or knowledge to go digging into that beast. Also, I'm not sure what interaction on my system is causing the problem. Clearly if Tino can run my testAccept.exe, then there has got to be something different...

Any suggestions anyone?

- J
Jeff Burch
Communications Solutions Department
Agilent Laboratories
Phone: 650-485-6364
Fax:     650-485-8092
email:   jeff_burch AT agilent DOT com

 -----Original Message-----
From: 	Tino Lange [mailto:Tino DOT Lange AT isg DOT de] 
Sent:	Thursday, February 13, 2003 2:56 PM
To:	jeff_burch AT agilent DOT com
Subject:	Re: Problem with accept(2) on the 1003.20.0.0 release

Hi!

I remeber some time ago hanging my sshd on the second connect if it was
bound to all interfaces.
Just a weird idea: Could you try to bind the server socket only to your
"real" IP and try again with telnet <ip> <port>?

Tino

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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019