Re: Bluetooth service - was manually fixing IPs
On Tue, 29 Mar 2011 17:34:39 -0500 Ian Pilcher wrote: 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 The bluez D-Bus service activates bluetooth.service directly. See /usr/share/dbus-1/system-services/org.bluez.service: ... SystemdService=bluetooth.service Compare this with org.freedesktop.NetworkManager.service which uses an indirect alias that can be enabled/disabled by systemctl: SystemdService=dbus-org.freedesktop.NetworkManager.service This was discussed in February on systemd-devel: http://lists.freedesktop.org/archives/systemd-devel/2011-February/001384.html Michal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Bluetooth service - was manually fixing IPs
Michal Schmidt (mschm...@redhat.com) said: Compare this with org.freedesktop.NetworkManager.service which uses an indirect alias that can be enabled/disabled by systemctl: SystemdService=dbus-org.freedesktop.NetworkManager.service This was discussed in February on systemd-devel: http://lists.freedesktop.org/archives/systemd-devel/2011-February/001384.html Note that this doesn't appear to be working right, or at least isn't implemented in NM the way an admin would expect: https://bugzilla.redhat.com/show_bug.cgi?id=691549 Bill -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Bluetooth service - was manually fixing IPs
On Tue, 29.03.11 14:39, Ian Pilcher (arequip...@gmail.com) wrote: On 03/29/2011 02:31 PM, Lennart Poettering wrote: Please paste systemctl show bluetooth.service, which should tell us what pulled it in. Here it is. Id=bluetooth.service Names=bluetooth.service Requires=systemd-logger.socket dbus.target basic.target Conflicts=shutdown.target Before=shutdown.target After=syslog.target systemd-logger.socket dbus.target basic.target It's not pulled in by anything at all according to this, so the disabling worked. Maybe something started it manually? Try to boot with systemd.log_level=debug systemd.log_target=kmsg log_buf_len=2M on the kernel cmdline. Then keep an eye on dmesg, look for bluetooth.service being mentioned. If you find something, tell me and paste those lines and the context around it and I might be able to tell you what activated it. Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Bluetooth service - was manually fixing IPs
On Tue, 29.03.11 14:54, Ian Pilcher (arequip...@gmail.com) wrote: On 03/29/2011 02:44 PM, Lennart Poettering wrote: Maybe something started it manually? Looks like it happens when I log in to KDE. I assume this means that KDE isn't using D-BUS to start the service, right? If it were, disabling it with systemctl would have worked. I have no idea what KDE does. If it really manually runs systemctl start bluetooth.service (or /sbin/service bluetooth start) then the KDE folks should stop doing that. They should respect system configuration, and not manually start something the admin explicitly didn't want to get started. Can you paste the kmsg context of the starting please? Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Bluetooth service - was manually fixing IPs
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 arequip...@gmail.com If you're going to shift my paradigm ... at least buy me dinner first. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
