Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Wed, 5 Sep 2001 10:18:26 +0200
From: Corinna Vinschen <cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: different lynx fix for: Alert!: Unable to connect to remote host
Message-ID: <20010905101826.A30380@cygbert.vinschen.de>
Mail-Followup-To: cygwin AT cygwin DOT com
References: <01b701c135ab$eceeb070$6601ffbf AT ashoka>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <01b701c135ab$eceeb070$6601ffbf@ashoka>; from mmoraes@teleias.com on Tue, Sep 04, 2001 at 06:41:42PM -0700

On Tue, Sep 04, 2001 at 06:41:42PM -0700, Mark Moraes wrote:
> Hi.
> 
> lynx's second "confirm-ready" connect returns EINVAL
> rather than EINPROGRESS on lynx 2.8.4-1 on my Win2K laptop,
> but worked fine on a (slower) Win98SE desktop, so
> it doesn't seem consistently reproducible. I'd speculate that it
> happens on faster machines (the laptop is a 650Mhz PIII and
> all the machines that were mentioned in past problem reports seem
> like moderately fast boxes)
> 
> I've seen several past references to this kind of problem in the list,
> but none of them seemed to solve it for me. The patch here is a kludge: the correct answer is probably to get cygwin connect
> to return EINPROGRESS (Corinna, is it possible that your
> fix from 1.1.6 mentioned in this URL is missing from 1.3?)

No, it's still there.  It's just that Winsock su**s!

The existing kludge in Cygwin's connect just translates Winsock's
WSAEWOULDBLOCK into the otherwise expected error code WSAEINPROGRESS.

After carefully reading the MSDN again, I have checked in a fix for
this case.  It turned out that reading skills are a big advantage. 
WSAEINVAL is a valid return code when using connect() on non-blocking
sockets in Winsock 1.1.

I'm really glad that you tracked that down!  The fix will show up in
the next developers snapshot and in Cygwin 1.3.3.

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