https://bugzilla.novell.com/show_bug.cgi?id=717162
https://bugzilla.novell.com/show_bug.cgi?id=717162#c24
Frederic Crozat changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
InfoProvider|fcrozat@suse.com |
--- Comment #24 from Frederic Crozat 2011-11-17 14:39:00 UTC ---
let's explicit this thing a little bit :
systemd doesn't automatically reload the various .service (or initscripts)
files when they change on disk, so there is a need to tell it when to refresh
its configuration (ie when those files changes).
bnc#728947 is when insserv is used on a sysvinit system with systemd installed
and in this case, the forward to systemd was trying to tell systemd to reload
disk configuration, which fails (since systemd doesn't run) and was causing a
error return code.
here, we are in a different situation : systemd is running, so /sbin/service
(through /etc/rc.status) is forwarding to systemd, to make sure initscripts are
correctly managed by systemd.
This means when a new package is installed, with a initscript, "something"
needs to tell systemd to "reload" disk configuration.
Since insserv is "the" standard way to enable / disable initscripts in package,
it would be logical it notifies systemd it should reload disk configuration
(another way could be to modify the initscripts relevant macros, but in this
case, it would require rebuilding all packages shipping initscripts).
Currently, when systemctl enable foo.service is used (foo being an initscript),
systemd correctly reload its configuration (unless --no-reload is used).
--
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.