http://bugzilla.opensuse.org/show_bug.cgi?id=968405 http://bugzilla.opensuse.org/show_bug.cgi?id=968405#c36 --- Comment #36 from Dominique Leuenberger <dimstar@opensuse.org> --- (In reply to Dr. Werner Fink from comment #34)
IMHO a list of services which should not be restarted may added to /etc/sysconfig/services then this list can be used to be skip exactly this services from getting restarted. Currently there are xdm and other display managers ... maybe sshd, and some others .. xen?
You favor a static list in a 'random' package over a package having the chance to specify by itself that it knows its service must not be restarted (the solution we had in place before with the exported variable).
(In reply to Dominique Leuenberger from comment #23)
Sorry but I prefere to get SLES and openSUSE in sync at this point. Even if this requires a veto from my side.
ath 'this' point or 'one' point again once we actually have a working solution? I agree of course that syncing it up is certainly the right thing to do. But so far we don't even have a clear answer what we want to achieve exactly.
From what I understood:
a) Per default, we want services to be restarted on updated / stopped on uninstall b) A system admin might want to change one or both behaviors (changing the values in /etc/sysconfig/services) c) Some packages KNOW that restarting their service has very severe side effects (xen tears down the VMs, apparmor leaves all running apps unprotected, PackageKit loses the running update task, xdm loses the running Desktop sessions). This list of packages is non-exhaustive and can/will change over time. *a* was never disputed and the existing macros clearly pointed into this direction. *b* did not work prior to the systemd-rpm-macros change of 'end of 2015' (the one referenced in comment 9) *c* did work until the same change, some argue by accident, some argue it was intentional (as some packages make use of it, one could also elevate the accident to a welcome behavior) The goal, imho, is to satisfy all three usecases. -- You are receiving this mail because: You are on the CC list for the bug.