From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] nonblocking connect : Wrong return code ?
Date: Sat, 04 Dec 2004 05:45:51 +0100 [thread overview]
Message-ID: <1102135551.8479.34.camel@pegasus> (raw)
In-Reply-To: <200412040251.25791.wim.delvaux@adaptiveplanet.com>
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
prev parent reply other threads:[~2004-12-04 4:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-04 1:51 [Bluez-users] nonblocking connect : Wrong return code ? wim delvaux
2004-12-04 4:45 ` Marcel Holtmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1102135551.8479.34.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox