Re: [Bluez-devel] bluez-utils 2.7 default configuration

Marcel Holtmann
2004-05-12T17:20:45Z

Hi David,

> > the bluez-utils-2.7 now contains sdpd, pand, dund and hidd. So there was
> > a need for a new init script that is able to start each of these daemons
> > on bootup. I enabled hidd by default, because it didn't harm if it is
> > started and hid2hci makes also sense. Why should it not be started?
>
> For the Fedora package I've put pand, dund and hidd in separate init
> scripts. It's expected that individual services can be enabled or
> disabled with chkconfig or system-config-services, rather than by
> manually editing a separate config file.
>
> Also, I've often been glad of being able to restart pand _separately_
> from hcid and sdpd. Doesn't sdpd forget _everything_ that's registered
> when you restart it?
>
> But hid2hci does make sense, assuming of course that you're not relying
> on a Bluetooth HID device without having the Linux BT-HID support
> working yet.

I have no problem with that, but for the upstream package I am going to
keep it this way. If you aren't a developer then you start the daemons
at boot and kill them at shutdown. That's all.

Regards

Marcel

-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.