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
Date: Wed, 26 Mar 2003 12:41:49 +0000
From: "Steven O'Brien" <steven DOT obrien2 AT ntlworld DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Failed non-blocking connect returns incorrect errno on AF_UNIX
 protocol
Message-Id: <20030326124149.53b06bc5.steven.obrien2@ntlworld.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit


On Wed, Mar 26, 2003 at 08:48:33AM +0800, David Huang wrote:
> Failed non-blocking connect returns incorrect errno on AF_UNIX
> protocol.

I think it is unlikely that the app really needs the connect() call to
be non-blocking (otherwise it would have to handle the in-progress
case). So a simple solution in most cases is to do the connect() first,
then the fcntl(fd, F_SETFL, O_NONBLOCK) so that data transfer is
non-blocking.

Regards,
Steven

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