https://bugzilla.novell.com/show_bug.cgi?id=656259
https://bugzilla.novell.com/show_bug.cgi?id=656259#c22
--- Comment #22 from Marius Tomaschewski
(In reply to comment #16)
... and this is the reason why /etc/rc.d/init.d/functions on a fedora host includes systemd support?
Sure they support legacy and third-party services. They are in the transition phase currently. sysv will go away for them, and all new stuff is expected to put sysv init scripts in sub rpms, that don't get installed by default, if really needed.
(In reply to comment #20)
(In reply to comment #16)
... and this is the reason why /etc/rc.d/init.d/functions on a feadora host includes systemd support? AFAIK if the `functions' file is sourced the sourcing script is redirected through systemctl
Here is the current Fedora guideline:
"Packages may also provide a SysV initscript file, but are not required to do so. This format is considered legacy, but Fedora still contains init mechanisms such as upstart which do not support the systemd unit file format. If present, the SysV initscript(s) must go into an optional subpackage, so as not to confuse sysadmins."
https://fedoraproject.org/wiki/TomCallaway/Systemd_Revised_Draft
Well, I don't really have any problem to make it same way -- but for 12.0 and not for 11.4, where we've released RC1 already and where it was not really possible to test on system running with systemd [I wrote a systemd dummy to make the initial syslog tests] for a too long time and there is not even a stable API/ABI for the daemons. Note: I know, it was not alone systemd fault, but there were problems with the kernel. So as far as I see, this bug tends to become a blocker for 12.0... -- 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.