From: Lars Grunewaldt <lgw@dark-reality.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] how do I disconnect btsco when the headset is gone/down ?
Date: Sun, 16 Jan 2005 01:25:55 +0100 [thread overview]
Message-ID: <41E9B493.5050102@dark-reality.de> (raw)
In-Reply-To: <pan.2005.01.15.17.32.11.742730@yahoo.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Paul Ionescu wrote:
| Hi all,
| Even if the headset is disconnected, the btsco program does not sense this
| fact and is still using the resources.
| I have to manually Ctrl-C or kill it.
|
| Is it only my case, or this is how is behaving right now ?
Yes, that is how it behaves. Maybe the socket wait should be changed so
it notices the RFCOMM disconnect properly?
regards,
~ Lars
- --
Lars Grunewaldt
* software development
* multimedia design
skills: C/C++/Java/PHP/(X)HTML/Flash/audio/video
web: http://www.dark-reality.de
mail: lgw@dark-reality.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFB6bSTQWC6DTWkDAoRAt7HAJ97txy6TegDufC4WC8VZ3EP5dZFVACfUYti
/xHDBYS1NmnKF2lTFcVk4To=
=Htga
-----END PGP SIGNATURE-----
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-01-16 0:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-15 17:32 [Bluez-devel] how do I disconnect btsco when the headset is gone/down ? Paul Ionescu
2005-01-16 0:25 ` Lars Grunewaldt [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=41E9B493.5050102@dark-reality.de \
--to=lgw@dark-reality.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.