RE: udev rule bluetooth.rules

[Marcel Holtmann <marcel@holtmann.org>]

Hi John,

> > Ref bluez-4.43 /etc/udev/bluetooth.rules:
> >
> > # Run helper every time a Bluetooth device appears
> > # On remove actions, bluetoothd should go away by itself
> > ACTION=="add", SUBSYSTEM=="bluetooth", RUN+="/usr/sbin/bluetoothd
> > --udev"
> >
> > Shouldn't this be of the format /etc/udev/rules.d/xx-bluetooth.rules
> > so that it starts in the correct order - i.e. after dbus?
> 
> That's taken care of - if dbus is not available, bluetoothd will exit
> with return code 1. udev will notice that and later start it again in
> the coldplug run.
> 
> > if dbus is not started, I need to do this:
> > # udevtrigger --subsystem-match=bluetooth
> > is this is what was meant by "coldplug run"?
> --
> Thanks - I'd been playing around with this as /etc/udev/rules.d/85-bluetooth.rules but hadn't got around to trying without dbus started - it works for me with dbus started.
> 
> It would be nice if "--prefix=/usr/local" were passed to bluetooth.rules to give:
> 
> ACTION=="add", SUBSYSTEM=="bluetooth", RUN+="/usr/local/sbin/bluetoothd

I fixed that now and we generate bluetooth.rules with the correct
prefix.

Regards

Marcel