On 03/29/2011 03:01 PM, Lennart Poettering wrote:
Can you paste the kmsg context of the starting please?
[ 42.087581] systemd[1]: Got D-Bus activation request for
bluetooth.service
[ 42.099029] systemd[1]: Trying to enqueue job
bluetooth.service/start/replace
[ 42.099342] systemd[1]: Installed new job bluetooth.service/start as 382
[ 42.099351] systemd[1]: Enqueued job bluetooth.service/start as 382
[ 42.099407] systemd[1]: About to execute: /usr/sbin/bluetoothd -n
[ 42.112528] systemd[1]: Forked /usr/sbin/bluetoothd as 2103
[ 42.112627] systemd[1]: bluetooth.service changed dead -> start
[ 42.168637] bluetoothd[2103]: bluetoothd[2103]: Bluetooth deamon 4.87
[ 42.183808] systemd[1]: Got D-Bus request:
org.freedesktop.DBus.NameOwnerChanged() on /org/freedesktop/DBus
[ 42.184485] systemd[1]: Got D-Bus request:
org.freedesktop.DBus.NameOwnerChanged() on
/org/freedesktop/DBusbluetoothd[2103]: bluetoothd[2103]:
Starting SDP server
[ 42.184491]
[ 42.184496] systemd[1]: bluetooth.service's D-Bus name org.bluez now
registered by :1.23
[ 42.184528] systemd[1]: bluetooth.service changed start -> running
[ 42.184536] systemd[1]: Job bluetooth.service/start finished, result=done
So it looks like it is being started via D-BUS, even though the service
is disabled. (I just re-re-re-verified that.)
--
========================================================================
Ian Pilcher arequipeno(a)gmail.com
"If you're going to shift my paradigm ... at least buy me dinner first."
========================================================================