[opensuse] Seemingly superfluous stuff running on 13.1
I have a desktop machine that I'm carefully trying out 13.1 on - I seem to have a few extra things running: /usr/sbin/ModemManager /usr/lib/bluetooth/bluetoothd /usr/sbin/wpa_supplicant This box has no bluetooth, yet a whole slew of bluetooth related software was installed, and even a daemon started. Doesn't YaST/something do a check on the types of hardware present and decides to install/not install the software to support it? I don't mind the extra packages, but I don't like running daemons for no reason. ModemManager ? https://bugzilla.novell.com/show_bug.cgi?id=717130 wpa_supplicant? There is no wifi on this box. I'm not using NetworkManager, but this all seems to suggest something NetworkManager related? -- Per Jessen, Zürich (-1.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 26/11/13 04:41, Per Jessen escribió:
I have a desktop machine that I'm carefully trying out 13.1 on - I seem to have a few extra things running:
/usr/sbin/ModemManager
You can remove ModemManager if you do not have any of the type of devices it supports.
/usr/lib/bluetooth/bluetoothd
you could remove bluez.
/usr/sbin/wpa_supplicant
required by Networkmamger Doesn't
YaST/something do a check on the types of hardware present and decides to install/not install the software to support it?
Yes but in this case, it can't ..
I'm not using NetworkManager, but this all seems to suggest something NetworkManager related?
Yes.. but.. yast cannot know if you are going to plug an USB wireless card , modem , bluetooth dongle afterwards.. -- "Judging by their response, the meanest thing you can do to people on the Internet is to give them really good software for free". - Anil Dash -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Cristian Rodríguez wrote:
El 26/11/13 04:41, Per Jessen escribió:
I have a desktop machine that I'm carefully trying out 13.1 on - I seem to have a few extra things running:
/usr/sbin/ModemManager
You can remove ModemManager if you do not have any of the type of devices it supports.
/usr/lib/bluetooth/bluetoothd
you could remove bluez.
/usr/sbin/wpa_supplicant
required by Networkmamger
Which I don't use. But yes, I'm deleting all of those.
Doesn't YaST/something do a check on the types of hardware present and decides to install/not install the software to support it?
Yes but in this case, it can't ..
I'm not using NetworkManager, but this all seems to suggest something NetworkManager related?
Yes.. but.. yast cannot know if you are going to plug an USB wireless card , modem , bluetooth dongle afterwards..
Yeah, okay - still doesn't seem right that the daemons are running. Isn't that something for systemd to start on-demand when the appropriate device is attached? -- Per Jessen, Zürich (-1.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 26/11/13 05:20, Per Jessen escribió:
Yeah, okay - still doesn't seem right that the daemons are running. Isn't that something for systemd to start on-demand when the appropriate device is attached?
the bluez stuff is (or was) supposed to work that way.. I believe networkmanager is not a suitable candidate for start on demand with systemd. -- "Judging by their response, the meanest thing you can do to people on the Internet is to give them really good software for free". - Anil Dash -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Cristian Rodríguez wrote:
El 26/11/13 05:20, Per Jessen escribió:
Yeah, okay - still doesn't seem right that the daemons are running. Isn't that something for systemd to start on-demand when the appropriate device is attached?
the bluez stuff is (or was) supposed to work that way.
Probably not worth opening a bugreport on.
I believe networkmanager is not a suitable candidate for start on demand with systemd.
Yes, but then I'm not running NM anyway. What about modemmanager and wpa-supplicant? Anyway, I've removed the software, I was mostly being curious. -- Per Jessen, Zürich (-0.8°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Dienstag, 26. November 2013 09:42:54 Per Jessen wrote:
Cristian Rodríguez wrote:
El 26/11/13 05:20, Per Jessen escribió:
Yeah, okay - still doesn't seem right that the daemons are running. Isn't that something for systemd to start on-demand when the appropriate device is attached?
the bluez stuff is (or was) supposed to work that way.
Probably not worth opening a bugreport on.
I believe networkmanager is not a suitable candidate for start on demand with systemd.
Yes, but then I'm not running NM anyway. What about modemmanager and wpa-supplicant? Anyway, I've removed the software, I was mostly being curious.
yast2 runlevel is your friend. Pete -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hans-Peter Jansen wrote:
On Dienstag, 26. November 2013 09:42:54 Per Jessen wrote:
Cristian Rodríguez wrote:
El 26/11/13 05:20, Per Jessen escribió:
Yeah, okay - still doesn't seem right that the daemons are running. Isn't that something for systemd to start on-demand when the appropriate device is attached?
the bluez stuff is (or was) supposed to work that way.
Probably not worth opening a bugreport on.
I believe networkmanager is not a suitable candidate for start on demand with systemd.
Yes, but then I'm not running NM anyway. What about modemmanager and wpa-supplicant? Anyway, I've removed the software, I was mostly being curious.
yast2 runlevel is your friend.
What help would it offer in this situation? It can't explain _why_ unneeded daemons were started :-) -- Per Jessen, Zürich (0.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 26/11/13 05:42, Per Jessen escribió:
the bluez stuff is (or was) supposed to work that way.
Probably not worth opening a bugreport on.
the spec file clears it up "# We need the bluez systemd service enabled at any time. It won't start up # on it's own, as it is triggered by udev in the end (bnc#796671)"
Yes, but then I'm not running NM anyway. What about modemmanager and wpa-supplicant? Anyway, I've removed the software, I was mostly being curious.
Both those are dbus-activated by NetworkManager. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Cristian Rodríguez wrote:
El 26/11/13 05:42, Per Jessen escribió:
Yes, but then I'm not running NM anyway. What about modemmanager and wpa-supplicant? Anyway, I've removed the software, I was mostly being curious.
Both those are dbus-activated by NetworkManager.
Huh? Does that mean that NetworkManager would need to be started in order for those two to be started? If so, something doesn't add up, coz' NetworkManager wasn't running on this system. -- Per Jessen, Zürich (-0.4°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Cristian Rodríguez -
Hans-Peter Jansen -
Per Jessen