* [Bluez-users] nonblocking connect : Wrong return code ?
@ 2004-12-04 1:51 wim delvaux
2004-12-04 4:45 ` Marcel Holtmann
0 siblings, 1 reply; 2+ messages in thread
From: wim delvaux @ 2004-12-04 1:51 UTC (permalink / raw)
To: bluez-users
when using a nonblocking socket,
when the connect is requested the errno that is returned is 11. (resource
temporarily unavailable)
Man page says that it should be EINPROGRESS (which is 115).
Man page for connect says :
EINPROGRESS :
The socket is non-blocking and the connection cannot be completed immediately.
It is possible to select(2) or poll(2) for completion by selecting
but
EAGAIN :
No more free local ports or insufficient entries in the routing cache
EAGAIN is a proper return code for this situations for read or write but not
for connect ...
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Bluez-users] nonblocking connect : Wrong return code ?
2004-12-04 1:51 [Bluez-users] nonblocking connect : Wrong return code ? wim delvaux
@ 2004-12-04 4:45 ` Marcel Holtmann
0 siblings, 0 replies; 2+ messages in thread
From: Marcel Holtmann @ 2004-12-04 4:45 UTC (permalink / raw)
To: BlueZ Mailing List
Hi Wim,
> when using a nonblocking socket,
>
> when the connect is requested the errno that is returned is 11. (resource
> temporarily unavailable)
>
> Man page says that it should be EINPROGRESS (which is 115).
>
> Man page for connect says :
>
> EINPROGRESS :
>
> The socket is non-blocking and the connection cannot be completed immediately.
> It is possible to select(2) or poll(2) for completion by selecting
>
> but
>
> EAGAIN :
>
> No more free local ports or insufficient entries in the routing cache
>
>
> EAGAIN is a proper return code for this situations for read or write but not
> for connect ...
we had this questions a long time ago and I never got a final answer
from anyone what is the right way to do. However the change must be done
in bt_sock_wait_state() and you must check rfcomm/sock.c, l2cap.c and
sco.c if it is still working as expected. Feel free to send in a patch
for it.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-12-04 4:45 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-12-04 1:51 [Bluez-users] nonblocking connect : Wrong return code ? wim delvaux
2004-12-04 4:45 ` Marcel Holtmann
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox