https://bugzilla.novell.com/show_bug.cgi?id=777418 https://bugzilla.novell.com/show_bug.cgi?id=777418#c11 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|werner@suse.com | --- Comment #11 from Dr. Werner Fink <werner@suse.com> 2012-11-16 09:44:08 UTC --- Hmmm ... insserv does calculate with the help of some graph theory the final dependency chains and write them out as makefiles together with installing the start/stop links for the services (hence the name insserv). It was never written to (re)start or reload a service. In past for this we had some other macros like %restart_on_update() and %stop_on_removal() for single services but not for restarting the service chains ... the question may rises how we use systemctl instead executing the SysVinit boot scripts. This because it could be required to ask the service its self with the help of systemctl what options are supported (reload, restart, try-restart, reload-or-restart, reload-or-try-restart) or required to enable the new configuration (daemon-reload). Btw: What are the side effect of a daemon-reload? As this recalculate the final dependency chains this may cause some side effects as restarting some serives (e.g. users may loose their X session, network connections, ...). -- 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.