Heads up: bluetoothd on-demand startup

Bastien Nocera bnocera at redhat.com
Fri Jun 12 19:20:22 UTC 2009


On Fri, 2009-06-12 at 14:39 -0400, Colin Walters wrote:
> On Fri, Jun 12, 2009 at 2:26 PM, Bastien Nocera<bnocera at redhat.com> wrote:
> >
> > bluetoothd will exit itself after 30 seconds when no adapters are
> > present. There's a potential race if the udev add event happens in
> > between the time the time the running bluetoothd reliquinshes its D-Bus
> > service, and the new one starts up.
> 
> We should support this I think.  I've added a bug here:
> 
> https://bugs.freedesktop.org/show_bug.cgi?id=22258

We don't use D-Bus for that in-flight message.

The message is in-flight between the kernel and bluetoothd via netlink.

   1. running bluetoothd           2. adapter insertion

- last bt adapter gets removed
- timeout kicks in
       30 sec...
- we start processing shutdown
                                   - udev gets event from the kernel
                                   - udev rule is processed
                                   - bluetoothd is run with --udev
                                   - bluetoothd exits because the
                                     service is already running
- relinquish the D-Bus service
- bluetoothd exits

Something like that.




More information about the devel mailing list