Bugzilla – Bug 846422
systemctl --type=service list-unit-files doesn't show LSB wrapped ones
Last modified: 2018-10-26 07:44:38 UTC
'systemctl --type=service list-unit-files' doesn't show LSB services which are showed only using 'systemctl --type=service list-units --all' which output on the other hand doesn't show whether services are enabled or not. Why major ship stopper: list-unit-files is used and parsed by YaST to provide service manager. Currently it only shows native systemd services, which we are still missing for some important services like xdm or MySQL. So fixing it to show even LSB services is quite crucial for 13.1 release. Other option would be to parse list-units command in YaST and call status on each of them, which would be quite slow and ugly work around.
*** Bug 840159 has been marked as a duplicate of this bug. ***
the description for "list-unit-files" is quite explicit in systemd manpage and it is a defined D-Bus API I can't modify without upstream approval (and it would requires a lot of changes, at least, until LSB initscripts handling is done with systemd generator, which is on systemd TODO list but not done yet). I've looked at how it is done in systemd-ui (http://cgit.freedesktop.org/systemd/systemd-ui/): - it is using D-Bus to access those informations (so no executable nor parsing involve) - it calls the D-BUS API equivalent to list-units --all and get D-Bus properties on each returned object to display.
Michal: the release manager sets ship stopper flag + or -. You're supposed to set the flag to ? with me in the input field behind it
(In reply to comment #3) > Michal: the release manager sets ship stopper flag + or -. You're supposed to > set the flag to ? with me in the input field behind it My bad, I told him to do it this way as I thought it is proper approach.
Ok, so you are saying that there is no easy way to make it behave same like list-units and that YaST guys has to find a different way how to detect states (query state for all LSB units manually or use D-Bus API), right? So back to YaST?
unfortunately, yes. Sorry :(
I disagree with the ship stopper status. 12.3 has no fully working system service editor either
*** Bug 845795 has been marked as a duplicate of this bug. ***
Vlado, to my knowledge you plan to change the behavior. Am I right?
(In reply to comment #9) > Vlado, to my knowledge you plan to change the behavior. Am I right? Yes, this is the proposal for including the lsb-wrapped services: https://github.com/yast/yast-services-manager/pull/33
This is an autogenerated message for OBS integration: This bug (846422) was mentioned in https://build.opensuse.org/request/show/205715 13.1 / yast2-services-manager
Maintenance request for opensuse-13.1:Update accepted.
openSUSE-RU-2013:1711-1: An update that has one recommended fix can now be installed. Category: recommended (low) Bug References: 846422 CVE References: Sources used: openSUSE 13.1 (src): yast2-services-manager-0.0.11-3.4.1