https://bugzilla.novell.com/show_bug.cgi?id=852312
https://bugzilla.novell.com/show_bug.cgi?id=852312#c3
--- Comment #3 from Joerg Diederich 2013-11-29 12:57:10 UTC ---
First of all I thought opensuse is going the direction to use systemd instead
of sysinit and systemctl is the new way to control the startup scripts. This
works fine with opensuse 12.3:
# opensuse 12.3:
root:~ # systemctl enable named.service
named.service is not a native service, redirecting to /sbin/chkconfig.
Executing /sbin/chkconfig named on
root:~ #
# opensuse 13.1:
root:/install/Linux/SuSE_13.1/pchafjd # systemctl enable named.service
named.service is not a native service, redirecting to /sbin/chkconfig.
Executing /sbin/chkconfig named on
The unit files have no [Install] section. They are not meant to be enabled
using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
Do you notice the difference? Why are things getting worse here? I have a bunch
of installation scripts, which were upgraded to use systemctl. Do I now have to
change those scripts again introducing some logic to decide whether I want to
control a systemd native service or a legacy one?
--
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.