Failed non-blocking connect returns incorrect errno on AF_UNIX protocol

[Steven O'Brien]

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/