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.
Lennart
--
Lennart Poettering Red Hat, Inc.
lennart [at] poettering [dot] net
http://0pointer.net/lennart/ GnuPG 0x1A015CC4