From: Stefan Mischke <survivor@uni-paderborn.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "BlueZ Mailing List" <bluez-devel@lists.sourceforge.net>,
"Bernd Eßmann" <psycho@uni-paderborn.de>
Subject: Re: [Bluez-devel] L2CAP: One failing connection hurts others?
Date: Thu, 16 Sep 2004 12:30:04 +0200 [thread overview]
Message-ID: <41496B2C.1030103@uni-paderborn.de> (raw)
In-Reply-To: <1095282542.19426.9.camel@pegasus>
Hi Marcel!
Marcel Holtmann schrieb:
>use the linger support of the L2CAP socket and put a "sleep 2" between
>the first and the second l2test call.
>
>
>
Your suggestions have no effect for me. Still errno 16. I think at the
moment it is not possible to connect concurrently via l2cap if one
device is down. But as a workaround I can use non-blocking connect (but
with a timeout of 60 seconds just to prevent deadlocks) and simply
reduce the pageto. My connection attempts are sequential anyway because
of the master-slave-limit. But I would suggest to change the behavior of
l2cap to allow more concurrent connection attempts even if some devices
are down.
Regards
Stefan
next prev parent reply other threads:[~2004-09-16 10:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 15:20 [Bluez-devel] L2CAP: One failing connection hurts others? Stefan Mischke
2004-09-14 18:34 ` Marcel Holtmann
2004-09-14 19:11 ` Stefan Mischke
2004-09-14 19:24 ` Marcel Holtmann
2004-09-14 19:37 ` Stefan Mischke
2004-09-14 19:49 ` Marcel Holtmann
2004-09-14 20:10 ` Stefan Mischke
2004-09-14 21:12 ` Marcel Holtmann
2004-09-14 23:37 ` Stefan Mischke
2004-09-15 7:46 ` Marcel Holtmann
2004-09-15 14:00 ` Stefan Mischke
2004-09-15 21:09 ` Marcel Holtmann
2004-09-15 22:26 ` Stefan Mischke
2004-09-16 10:30 ` Stefan Mischke [this message]
2004-09-16 10:34 ` Marcel Holtmann
2004-09-16 10:39 ` Stefan Mischke
2004-09-16 11:00 ` Marcel Holtmann
2004-09-16 11:10 ` Stefan Mischke
2004-09-16 16:41 ` Stefan Mischke
2004-09-15 20:37 ` Stefan Mischke
2004-09-15 21:06 ` Marcel Holtmann
2004-09-15 22:13 ` Stefan Mischke
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=41496B2C.1030103@uni-paderborn.de \
--to=survivor@uni-paderborn.de \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@holtmann.org \
--cc=psycho@uni-paderborn.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.