-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2014-09-30 12:56, Andreas Mahel wrote:
The SysVInit scripts are being "intercepted" by /etc/rc.status.
Let us clarify that this file has existed for many years, maybe decades. It was used with initd previously, and it is not part of the systemd package, but of aaa_base. Ie, it is an openSUSE thing. The changelog is full of suse.com/de addresses, not upstream.
This script has been extended to first check if systemd is installed, and if the script qualifies for being handled by systemd directly. If yes, the process is switching to systemctl: exec /bin/systemctl ${SYSTEMCTL_OPTIONS} $1 "${_rc_base}"
So it is not that systemd is intercepting the init scripts, but that the functionality of a file that is included by initd scripts since ever, has been extended, and as you say, if it finds systemd installed it then tells it to take over - as it must, obviously, at least as long as the system uses system as PID 1. So, no conspiration ;-)
While this is in fact not the prettiest solution, and makes it a little harder to find out how this works. On the other hand, as I see it, this mechanism exists only for backward compatibility reasons, and actually provides an elegant way to allow the software packager to provide both SysVInit scripts and systemd units, which can be used with either init daemon without change (so actually, there's no need to touch existing and working SysVInit scripts at all). However, if systemd is being used as the init daemon, systemd will be used to start the service.
Yep. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlQqvvIACgkQja8UbcUWM1xXZQD+MbX2Cbjoy/57Z4ATqIFNP8N5 NNfm+eA8+FeRuQD+mnAA/0gmvDW2wasyRky/zG7zdjQfNi055bGkAL0iGWtWKg6o =TfAg -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org