public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Carlos AM" <Carlos@naxus.biz>
To: "lista bluez" <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] modify RFCOMM_DISC_TIMEOUT
Date: Thu, 22 Jul 2004 16:19:54 +0200	[thread overview]
Message-ID: <000a01c46ff6$f6013a10$5000005a@naxus> (raw)

[-- Attachment #1: Type: text/plain, Size: 341 bytes --]

Hi

I am developing a GPS unit that communicates via RFCOMM and I noticed that the timeout of the RFCOMM disconnection is 20 seconds.
¿Does exists a way to change this timeout from a rfcomm server program that uses sockets?
It seems that changing this #define in the rfcomm.h is not enough

Regards
Carlos AM
Naxus Conectividad Móvil

[-- Attachment #2: Type: text/html, Size: 972 bytes --]

             reply	other threads:[~2004-07-22 14:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-22 14:19 Carlos AM [this message]
2004-07-22 17:32 ` [Bluez-devel] modify RFCOMM_DISC_TIMEOUT Marcel Holtmann
     [not found]   ` <003b01c47095$488aa3e0$5000005a@naxus>
2004-07-23  9:39     ` Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2004-07-28 12:12 Carlos AM
2004-07-28 12:22 ` 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='000a01c46ff6$f6013a10$5000005a@naxus' \
    --to=carlos@naxus.biz \
    --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