From: Marcel Holtmann <marcel@holtmann.org>
To: amine@baracoda.com
Cc: Halam Rose <halam.rose@7layers-uk.com>,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Rfcomm problem
Date: Fri, 09 Apr 2004 18:09:25 +0200 [thread overview]
Message-ID: <1081526964.21596.3.camel@pegasus> (raw)
In-Reply-To: <33118.82.127.5.232.1081513927.squirrel@baracoda.com>
Hi Amine,
> thanks for your answer, but i found the problem.
>
> i don't execute the script that generate the rfcomm devices.
this reminds me of a race that a normal user can't release a previous
created RFCOMM TTY if no device node is found and so the connection
still exists, but nobody can use it. The fix for the rfcomm utility is
already in CVS and the kernel update will be part of my big easter
update.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-04-09 16:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 14:49 [Bluez-devel] New BQB Halam Rose
2004-04-09 11:44 ` [Bluez-devel] rfcomm Problem amine
2004-04-09 11:49 ` [Bluez-devel] Rfcomm problem amine
2004-04-09 12:05 ` Marcel Holtmann
2004-04-09 12:32 ` amine
2004-04-09 16:09 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-01 23:12 [Bluez-devel] RFCOMM problem zubiwat
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=1081526964.21596.3.camel@pegasus \
--to=marcel@holtmann.org \
--cc=amine@baracoda.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=halam.rose@7layers-uk.com \
/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