From: Bastien Nocera <hadess@hadess.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Cc: Bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-devel] sdp not starting
Date: Fri, 01 Feb 2008 11:53:41 +0000 [thread overview]
Message-ID: <1201866821.2389.316.camel@cookie.hadess.net> (raw)
In-Reply-To: <530812.29878.qm@web8414.mail.in.yahoo.com>
On Fri, 2008-02-01 at 17:16 +0530, pramod gurav wrote:
> hi all
> i am not able to start the sdp daemon. These are the meesages i get
> in /var/log/messages :
> Feb 1 17:12:23 localhost hcid[31049]: HCI dev 0 registered
> Feb 1 17:12:23 localhost hcid[31049]: HCI dev 0 up
> Feb 1 17:12:23 localhost hcid[31049]: Device hci0 has been added
> Feb 1 17:12:23 localhost hcid[31049]: Starting security manager 0
> Feb 1 17:12:23 localhost hcid[31049]: Device hci0 has been activated
> Feb 1 17:12:54 localhost sdpd[31717]: Bluetooth SDP daemon
> Feb 1 17:12:54 localhost sdpd[31717]: Starting SDP server
> Feb 1 17:12:54 localhost sdpd[31717]: binding L2CAP socket: Address
> already in use
> Feb 1 17:12:54 localhost sdpd[31717]: Server initialization failed
>
>
> What is the reason
> Can anyone help me in sorting this?
You're probably already using the SDP server built into hcid (by passing
the "-s" argument to hcid), so it's normal that it fails.
Cheers
-------------------------------------------------------------------------
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/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-02-01 11:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 11:46 [Bluez-users] sdp not starting pramod gurav
2008-02-01 11:53 ` Bastien Nocera [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-01 12:18 [Bluez-devel] " pramod gurav
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=1201866821.2389.316.camel@cookie.hadess.net \
--to=hadess@hadess.net \
--cc=Bluez-users@lists.sourceforge.net \
--cc=bluez-devel@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