http://bugzilla.suse.com/show_bug.cgi?id=1093029
http://bugzilla.suse.com/show_bug.cgi?id=1093029#c15
Jiri Srain changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(jsrain@suse.com) |
--- Comment #15 from Jiri Srain ---
I agree, if it is about a few seconds, it should not be a big deal.
I still can remember a service which - in some cases - needed minutes to start
(cups had to do initial build of its database).
As long as systemctl call suceeds, YaST has no control over what is going on.
If it really is an issue, than IMO the systemctl call should wait until the
service is operational.
Ensuring a service is operational could result in an infinite wait - imagine
that it crashed between starting and the check itself.
--
You are receiving this mail because:
You are on the CC list for the bug.