From owner-freebsd-hackers  Wed May 22 15:44:15 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id PAA05089
          for hackers-outgoing; Wed, 22 May 1996 15:44:15 -0700 (PDT)
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA05078
          for <freebsd-hackers@freebsd.org>; Wed, 22 May 1996 15:44:12 -0700 (PDT)
Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <15499(7)>; Wed, 22 May 1996 15:43:26 PDT
Received: from localhost ([127.0.0.1]) by crevenia.parc.xerox.com with SMTP id <177475>; Wed, 22 May 1996 15:43:22 -0700
X-Mailer: exmh version 1.6.4 10/10/95
To: kbracey@art.acorn.co.uk (Kevin Bracey)
cc: freebsd-hackers@freebsd.org
Subject: Re: Problem with non-blocking TCP connects? 
In-reply-to: Your message of "Thu, 16 May 1996 03:02:50 PDT."
             <319B0B5A@kbracey> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 22 May 1996 15:43:19 PDT
From: Bill Fenner <fenner@parc.xerox.com>
Message-Id: <96May22.154322pdt.177475@crevenia.parc.xerox.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <319B0B5A@kbracey> you write:
>There is an interesting anomaly in the processing of non-blocking TCP
>connections.

I'm not convinced that calling connect() again is the right thing to do to see 
if it has completed.  I tend to select() for writing (as implied by the 
connect(2) man page), and then use getsockopt(SO_ERROR) when the select comes 
true.

  Bill