This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Failed non-blocking connect returns incorrect errno on AF_UNIX protocol
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 26 Mar 2003 09:52:21 +0100
- Subject: Re: Failed non-blocking connect returns incorrect errno on AF_UNIX protocol
- References: <3E80F8E1.2000409@linuxforum.net>
- Reply-to: cygwin at cygwin dot com
On Wed, Mar 26, 2003 at 08:48:33AM +0800, David Huang wrote:
> Failed non-blocking connect returns incorrect errno on AF_UNIX protocol.
> See attached test program.
>
> On cygwin:
> $ ./afunix
> EINPROGRESS: Operation now in progress
>
> On
> Linux 2.4 (Debian 2.2)
> Linux 2.4 (Redhat 7.3)
> Sun Solaris (8):
> $ ./afunix
> ECONNREFUSED: Connection refused
>
> When i comment following code:
> // if (fcntl (fd2, F_SETFL, O_NONBLOCK) < 0)
> // printf ("Failed to set fd non-blocking");
> The result is
> ECONNREFUSED: Connection refused
>
> It seems an old bug.
> I don't know whether it effect others address/protocol families.
I don't see that it's an error. On non-blocking sockets you have to
expect that connect() returns before being connected. Just because
other systems are so quick figuring out that nothing is listening on
the other side, this doesn't invalidate the EINPROGRESS response under,
well, slower conditions.
And, btw., SUSv3 doesn't say a word that EINPROGRESS is not a valid
response for AF_LOCAL sockets.
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/