On Sun, 5 Jul 2009 12:24:34 +0200 John Frankish <j-frankish@xxxxxxx> wrote: > 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. -- Stefan Seyfried R&D Preload Department | "Any ideas, John?" SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out." This footer brought to you by insane German lawmakers: SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
