From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Can't connect RFCOMM socket:Resourcetemporarilyunavailable
Date: Fri, 24 Aug 2007 16:27:01 +0200 [thread overview]
Message-ID: <1187965621.15402.179.camel@violet> (raw)
In-Reply-To: <d5920d1e0708240706t22fd0f73p29220630ed9a7644@mail.gmail.com>
Hi Hamid,
> I think it's better that I give you all the output I got from the
> beginning in order to understand better the situation.
actually hcidump works like tcpdump. You have to run it in a different
terminal. Otherwise it is useless.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-08-24 14:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 6:07 [Bluez-users] Can't connect RFCOMM socket: Resource temporarilyunavailable jaspreet singh
2007-08-22 7:58 ` Hamid MENOUAR
2007-08-22 14:26 ` [Bluez-users] Can't connect RFCOMM socket: Resourcetemporarilyunavailable jaspreet singh
2007-08-22 14:56 ` Hamid MENOUAR
2007-08-22 15:55 ` [Bluez-users] Can't connect RFCOMM socket:Resourcetemporarilyunavailable jaspreet singh
2007-08-24 12:18 ` Marcel Holtmann
2007-08-24 14:06 ` Hamid MENOUAR
2007-08-24 14:27 ` Marcel Holtmann [this message]
2007-08-24 14:47 ` Hamid MENOUAR
2007-08-24 14:59 ` Marcel Holtmann
2007-08-24 15:09 ` Hamid MENOUAR
2007-09-05 10:47 ` [Bluez-users] Can't connect RFCOMM socket: Resource temporarilyunavailable Xamindar
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=1187965621.15402.179.camel@violet \
--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