https://bugzilla.novell.com/show_bug.cgi?id=769946 https://bugzilla.novell.com/show_bug.cgi?id=769946#c0 Summary: YaST2 Service::Enable[d]("foo") no longer works in case of systemd Classification: openSUSE Product: openSUSE 12.2 Version: Beta 2 Platform: All OS/Version: openSUSE 12.2 Status: NEEDINFO Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: msvec@suse.com ReportedBy: jsmeix@suse.com QAContact: jsrain@suse.com CC: badshah400@gmail.com, fcrozat@suse.com InfoProvider: fcrozat@suse.com Found By: Development Blocker: --- For the history see https://bugzilla.novell.com/show_bug.cgi?id=769346#c13 Michal Svec, I assigned this issue initially to you because according to https://github.com/yast/yast-yast2/blame/master/library/runlevel/src/Service... you are one of those who currently work on Service.ycp. In the YaST printer module in printer/src/Printerlib.ycp I call Service::Enabled("cups") to test if the service cups is enabled to be started during boot and if it is not enabled I call Service::Enable("cups") to enable that the service cups is started during boot. It seems somehow this does not work if systemd is used. It works if SysVinit is used. As far as I see Service::Enable[d] is implemented in yast2/library/runlevel/src/Service.ycp and therein it seems it runs basically /sbin/chkconfig -l cups | /usr/bin/grep -q '[0-6]:on' When I run this on my openSUSE 12.2 beta2 test machine I get ---------------------------------------------------------------------------- # /sbin/chkconfig -l cups Note: This output shows SysV services only and does not include native systemd services. SysV configuration data might be overridden by native systemd configuration. cups 0:off 1:off 2:on 3:on 4:off 5:on 6:off # /sbin/chkconfig -l cups | /usr/bin/grep -q '[0-6]:on' \ && echo enabled || echo disabled Note: This output shows SysV services only and does not include native systemd services. SysV configuration data might be overridden by native systemd configuration. enabled ---------------------------------------------------------------------------- Nevertheless after a reboot, cupsd is not running. Some time ago crrodriguez@opensuse.org had added "complete systemd support" to the cups package which now provides /lib/systemd/system/cups.path /lib/systemd/system/cups.service /lib/systemd/system/cups.socket in addition to its traditional SysVinit setup via -------------------------------------------------------------------- %post %{fillup_and_insserv -ny cups cups} -------------------------------------------------------------------- in cups.spec which must stay there to be backward compatible. According to how I understand the above "Note:" in the chkconfig output it means that chkconfig is no longer the right tool for services which have a native systemd configuration. If my analysis is right, the question is must Service.ycp be adapted so that all the YaST modules which use it still work even if a service gets a native systemd configuration or must /sbin/chkconfig be adapted so that it also works even if a service gets a native systemd configuration or must all YaST modules which call Service::... functions be adapted to work even if a service gets a native systemd configuration or must something in the cups package be adapted so that it still works for both systems with SysVinit and with systemd? I do not know how to solve this because I am not a SysVinit expert and not at all a systemd expert. Frederic Crozat, could you provide uesful information how to solve this? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.