Subject: Re: [Bluez-devel] hcid hotplug initialisation?
From: Marcel Holtmann <marcel@holtmann.org>
To: Fredrik Noring <noring@nocrew.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
In-Reply-To: <1076323204.5263.34.camel@kalkyl.roxen.com>
References: <1076323204.5263.34.camel@kalkyl.roxen.com>
Content-Type: text/plain
Message-Id: <1076323641.6869.98.camel@pegasus>
Mime-Version: 1.0
Sender: bluez-devel-admin@lists.sourceforge.net
Errors-To: bluez-devel-admin@lists.sourceforge.net
Date: Mon, 09 Feb 2004 11:47:21 +0100

Hi Fredrik,

> Regarding hcid initilisation, what about having the hotplug stuff
> starting hcid instead of /etc/init.d/hcid? 
> 
> That way hcid can be installed without using cpu/memory resources
> and it will work automatically when a user inserts some Bluetooth
> device.

no. The bluetooth.agent is only for device specific configuration and
not for starting a deamon. However hcid watches all interfaces and
bluetooth.agent would be called for every device. Multiple running
hcid's will mess up the security manager.

Regards

Marcel


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel