From: kwyjibo@ono.com
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Socket error: No such file or directory
Date: Fri, 3 Dec 2004 17:57:24 +0100 [thread overview]
Message-ID: <41A705AA000053C5@mta02.ono.com> (raw)
Hi,
I'm trying to open a socket with this:
servSockBluez =3D socket(PF_BLUETOOTH, SOCK_STREAM, BTPROTO_RFCOMM)
but I get an error: "No such file or directory", wich I don't understant
it at all.
What's exactly the problem?
Thanks in advance.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2004-12-03 16:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-03 16:57 kwyjibo [this message]
2004-12-03 17:06 ` [Bluez-devel] Socket error: No such file or directory Marcel Holtmann
2004-12-03 17:09 ` Stephen Crane
2004-12-04 6:53 ` Marcel Holtmann
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=41A705AA000053C5@mta02.ono.com \
--to=kwyjibo@ono.com \
--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