On Fri, 2009-06-12 at 21:52 +0200, Lennart Poettering wrote:
On Fri, 12.06.09 20:10, Bastien Nocera (bnocera(a)redhat.com) wrote:
> > This could be fixed by first releasing the service name synchronously,
> > then processing all queued requests and only then closing/exiting.
> >
> > Hmm, will bluetoothd also be started via bus activation? If so, it
> > wuld probably make sense to issue a StartByName D-Bus request from the
> > udev rule and let dbus handle all the ordering/synchronization issues
> > with starting up bluetoothd.
>
> No, there's no service activation support. Would it be useful?
I think it would. Seems to me as if some of the BT functionality
(org.bluez.Manager, ...) might be useful even without having hw
plugged in.
All the API in doc/manager-api.txt shows that org.bluez.Manager's sole
purpose is to tell you about available Adapters, and enumerate them.
It's useless without an adapter plugged in.