[corinna-cygwin@cygwin.com: Re: Failed non-blocking connect returns incorrect errno on AF_UNIX protocol]
Corinna Vinschen
vinschen@redhat.com
Thu Mar 27 08:38:00 GMT 2003
Did you see this, Thomas?
AFAICS, the solution would probably be to switch to blocking as you
suggested yesterday. On a quick glance I don't see another reliable
way to get the desired behaviour otherwise.
Sic,
Corinna
----- Forwarded message from Corinna Vinschen <corinna-cygwin@cygwin.com> -----
> Date: Thu, 27 Mar 2003 09:33:27 +0100
> From: Corinna Vinschen <corinna-cygwin@cygwin.com>
> Subject: Re: Failed non-blocking connect returns incorrect errno on AF_UNIX protocol
> To: cygwin@cygwin.com
> Reply-To: cygwin@cygwin.com
>
> On Thu, Mar 27, 2003 at 10:32:16AM +0800, David Huang wrote:
> > Corinna Vinschen wrote:
> > >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.
> > Well, in my test-case, /tmp/.afunix is a dead socket, connect must return
> > ECONNREFUSED but not EINPROGRESS, is it so?
>
> Yes, you're right but this information is missing in your previous
> posting. I see why this happens but I don't have a quick solution.
>
> However, thanks for the report,
> Corinna
>
> --
> Corinna Vinschen Please, send mails regarding Cygwin to
> Cygwin Developer mailto:cygwin@cygwin.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/
----- End forwarded message -----
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin@cygwin.com
Red Hat, Inc.
More information about the Cygwin-developers
mailing list