From: Jose Vasconcellos <jose@vasmac.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] New bluetooth-headset release 20061109 : nickname 'dogfood' ; -)
Date: Tue, 21 Nov 2006 15:39:27 -0500 [thread overview]
Message-ID: <456363FF.7070801@vasmac.com> (raw)
In-Reply-To: <45635BFD.7070404@free.fr>
Hi Fabien,
Please take a look at file /proc/net/unix.
It lists all opened sockets. If headsetd is running,
it's easy to tell because that is the only one that
has a string of nul characters following the name.
My patch fixes that.
Jose
-------------------------------------------------------------------------
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-11-21 20:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 20:42 [Bluez-devel] New bluetooth-headset release 20061109 : nickname 'dogfood' ; -) Fabien Chevalier
2006-11-20 22:33 ` Jose Vasconcellos
2006-11-20 23:06 ` Brad Midgley
2006-11-21 7:35 ` Marcel Holtmann
2006-11-21 15:03 ` [Bluez-devel] SCO flow control (Was: New bluetooth-headset release 20061109) Jose Vasconcellos
2006-11-21 15:26 ` Marcel Holtmann
2006-11-21 17:26 ` Jose Vasconcellos
2006-11-21 17:53 ` Marcel Holtmann
2006-11-21 18:52 ` [Bluez-devel] New bluetooth-headset release 20061109 : nickname 'dogfood' ; -) Jose Vasconcellos
2006-11-21 20:05 ` Fabien Chevalier
2006-11-21 20:39 ` Jose Vasconcellos [this message]
2006-11-22 11:12 ` Fabien Chevalier
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=456363FF.7070801@vasmac.com \
--to=jose@vasmac.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 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.