public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Mark S. Townsley" <mstownsley@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] RFCOMM error
Date: Thu, 21 Sep 2006 12:41:41 -0700	[thread overview]
Message-ID: <be976db60609211241r54ccbf5k7da10f8ffaa5a695@mail.gmail.com> (raw)
In-Reply-To: <1158867330.11194.50.camel@localhost>


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

Many thanks.  That fixed the problem....

Mark

On 9/21/06, Marcel Holtmann <marcel@holtmann.org> wrote:
>
> Hi Mark,
>
> > I have a an RFCOMM server process listening on one box.  From a Linux
> > laptop,
> > I just wrote a simple RFCOMM client to connect to it.  Very simple,
> > via AF_BLUETOOTH, SOCK_SEQPACKET and
> > BTPROTO_RFCOMM.
> >
> > I got back errno as Bad File Descriptor.  When I strace it, I saw this
> > line:
> >
> >    socket(PF_BLUETOOTH, SOCK_SEQPACKET, 3) = -1  ESOCKTNOSUPPORT
> > (Socket type not supported).
> >
> > What does that mean?  Did I construct the socket wrong?
>
> for RFCOMM it must be SOCK_STREAM.
>
> Regards
>
> Marcel
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>

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

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

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

[-- 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:[~2006-09-21 19:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-21 19:30 [Bluez-users] RFCOMM error Mark S. Townsley
2006-09-21 19:35 ` Marcel Holtmann
2006-09-21 19:41   ` Mark S. Townsley [this message]

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=be976db60609211241r54ccbf5k7da10f8ffaa5a695@mail.gmail.com \
    --to=mstownsley@gmail.com \
    --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