The file /etc/udev/rules.d/70-bluetooth.rules tells udev to run /lib/udev/bluetooth.sh which again launches /etc/init.d/bluetooth upon if certain devices (/devhdc[0-9]) pops up. This happens even if I do not have bluetooth set in my runlevel, which is a bug. Also, since it is not in my runlevel, rc-status does not display it. Just because I happen to have some bluetooth hardware available and bluez installed, does not mean that I _always_ want it to be launched. Reproducible: Always Steps to Reproduce: 1. have a system with udev, bluetooth hardware and kernel modules for it 2. install bluez (inkl bluez-utils) 3. do not have bluetooth in your runlevel (typically "default") Actual Results: "/etc/init.d/bluetooth status" says it is started Expected Results: "/etc/init.d/bluetooth status" says it is stopped
That's a feature, not a bug. You can blacklist it or use RC_PLUG_SERVICES/RC_HOTPLUG in /etc/conf.d/rc if you don't want such stuff.
