public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Miguel <mc354@tid.es>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Can't connect RFCOMM socket: Permission denied
Date: Tue, 29 Jan 2008 15:01:33 +0100	[thread overview]
Message-ID: <1201615293.14284.39.camel@McM> (raw)
In-Reply-To: <80662.65756.qm@web8404.mail.in.yahoo.com>


[-- Attachment #1.1: Type: text/plain, Size: 293 bytes --]

you have to release the port

rfcomm release 0

and then connect again

On Tue, 2008-01-29 at 19:25 +0530, pramod gurav wrote:

> for HS BT device on my system it shows an error
> [Pramod@localhost ~]$ sudo rfcomm connect 0 00:0F:DE:B1:02:42
> Can't create RFCOMM TTY: Address already in use 

[-- Attachment #1.2: Type: text/html, Size: 687 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2008-01-29 14:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-29 13:55 [Bluez-users] Can't connect RFCOMM socket: Permission denied pramod gurav
2008-01-29 14:01 ` Miguel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-29 14:14 pramod gurav
2008-01-29 14:59 ` Miguel
2008-01-29 14:08 pramod gurav
2008-01-29 14:11 ` Johan Hedberg
2008-01-29 13:07 pramod gurav
2008-01-29 13:25 ` Miguel

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=1201615293.14284.39.camel@McM \
    --to=mc354@tid.es \
    --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