linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Cc: bluez-devel@lists.sf.net
Subject: Re: [Bluez-devel] sdpd deamon fails to start.
Date: Sat, 03 Dec 2005 14:38:10 +0100	[thread overview]
Message-ID: <1133617090.31106.41.camel@blade> (raw)
In-Reply-To: <4391A0A9.5090706@ncoretech.com>

Hi Zaheer,

> I have installed the bluez utilities on my embedded linux system.
> However when I start "sdpd" I get the following error.
> 
> Jan 31 03:32:31 Simputer daemon.info hcid[1298]: Bluetooth HCI daemon
> Jan 31 03:32:31 Simputer daemon.info hcid[1298]: HCI dev 0 up
> Jan 31 03:32:31 Simputer daemon.info hcid[1298]: Starting security manager 0
> Jan 31 03:32:33 Simputer daemon.err sdpd[1369]: init_server: binding 
> UNIX socket: No such file or directory
> Jan 31 03:32:33 Simputer daemon.err sdpd[1369]: main: Server 
> initialization failed

it wants to create a Unix domain socket at /var/run/sdp and it must have
permissions for that.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-12-03 13:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-03 13:42 [Bluez-devel] sdpd deamon fails to start Zaheer Ahamed
2005-12-03 13:38 ` Marcel Holtmann [this message]
2005-12-03 14:08   ` Zaheer Ahamed
2005-12-03 14:09     ` Marcel Holtmann
2005-12-03 14:42     ` Zaheer Ahamed

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=1133617090.31106.41.camel@blade \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sf.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;
as well as URLs for NNTP newsgroup(s).