Return-Path: Message-ID: <22b6c3510706280736h6367a25eiac4918c0f80497a2@mail.gmail.com> Date: Thu, 28 Jun 2007 22:36:40 +0800 From: "Benjamin Fong" To: "BlueZ development" MIME-Version: 1.0 Subject: [Bluez-devel] hcid defunct Reply-To: BlueZ development List-Id: BlueZ development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2036104761==" Sender: bluez-devel-bounces@lists.sourceforge.net Errors-To: bluez-devel-bounces@lists.sourceforge.net --===============2036104761== Content-Type: multipart/alternative; boundary="----=_Part_58978_32946717.1183041400343" ------=_Part_58978_32946717.1183041400343 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, I've written a program which periodically invokes hcitool scan, and following that propagate out content via obex to the acquired bluetooth address. I've noticed something remarkably strange occuring throughout the process. The program which I'd written is invoked immediately after boot. I'd noticed when I "ps -e" my system, there are a couple of defunct hcid processes. These defunct hcid jobs are immediately visible right after boot and the amount of defunct hcid process will to continue grow until the entire bluetooth service is stuffed. Once the bluetooth srvice is stuffed, if I were to invoke either hcitool or sdptool...I would get a "connection timeout" reply. The only way to remedy the situation is to periodically restart the bluetooth service, once the service is restarted - all of the defunct hcid process will be cleared. Btw I'm running Bluez-utils and bluez-libs 3.10.1 on both Fedora 6 and 7 (issue is replicatable on both system). I've multiple dongles, but only 1 dongle dedicated to scanning. Any idea, guys? Regards, Ben ------=_Part_58978_32946717.1183041400343 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Hi,
 
I've written a program which periodically invokes hcitool scan, and following that propagate out content via obex to the acquired bluetooth address. I've noticed something remarkably strange occuring throughout the process. The program which I'd written is invoked immediately after boot. I'd noticed when I "ps -e" my system, there are a couple of defunct hcid processes. These defunct hcid jobs are immediately visible right after boot and the amount of defunct hcid process will to continue grow until the entire bluetooth service is stuffed. Once the bluetooth srvice is stuffed, if I were to invoke either hcitool or sdptool...I would get a "connection timeout" reply. The only way to remedy the situation is to periodically restart the bluetooth service, once the service is restarted - all of the defunct hcid process will be cleared.
 
Btw I'm running Bluez-utils and bluez-libs 3.10.1 on both Fedora 6 and 7 (issue is replicatable on both system). I've multiple dongles, but only 1 dongle dedicated to scanning. Any idea, guys?
 
Regards,
Ben
------=_Part_58978_32946717.1183041400343-- --===============2036104761== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ --===============2036104761== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel --===============2036104761==--