On Mon, 23 Nov 2015 11:37:42 -0600
Neil Rickert
Yesterday, I did a clean install of snapshot 20151118.
After installing, I went to setup autofs. So I started Yast services manager. Then I went to the "rpcbind" line and clicked "Start". Nothing seemed to happen on the screen. So I clicked "enable". Again, nothing seemed to happen.
I then tried the same changes for "autofs". Again, nothing seemed to happen on the screen.
So I clicked "Finish" (or maybe it was "Next"). Then I restarted Services manager, and it did now show the services as running.
Is this intended? Are we supposed to blindly configure services and check later? Or is this a recently introduced bug?
Previous experience is that when I click "Start", the service changes to show as "Active" and the "Start" button changes to "Stop". But that did not happen here.
My suspicion is that start cause service to fail, so it is not really started (old sysV failed when start fail, but with systemd it succeed, so it need additional check which we maybe forgot). To be sure, we need your y2log, which can show what happen with service start call. Josef -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org