https://bugzilla.novell.com/show_bug.cgi?id=852312 https://bugzilla.novell.com/show_bug.cgi?id=852312#c1 --- Comment #1 from Joerg Diederich 2013-11-28 20:32:21 UTC --- Same issue using "systemctl enable ntp.service". It seems to be a problem with systemctl in combination with legacy init scripts. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=852312 https://bugzilla.novell.com/show_bug.cgi?id=852312#c2 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |werner@suse.com Resolution| |WORKSFORME --- Comment #2 from Dr. Werner Fink 2013-11-29 07:51:34 UTC --- What is wrong with insserv named or chkconfig named on beside this linux /suse/werner> sudo -i linux:~ # systemctl enable raw.service raw.service is not a native service, redirecting to /sbin/chkconfig. Executing /sbin/chkconfig raw 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, ...). you may see the third and fourth line with raw.service is not a native service, redirecting to /sbin/chkconfig. Executing /sbin/chkconfig raw on -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=852312 https://bugzilla.novell.com/show_bug.cgi?id=852312#c4 --- Comment #4 from Dr. Werner Fink 2013-11-29 13:06:04 UTC --- (In reply to comment #3) This is what upstream does ... why do you think I should change that? Please provide a reason for doing that. If you think this is a bug then please report it upstream: https://bugs.freedesktop.org/enter_bug.cgi?product=systemd as then this will be fixed without maintaining a further patch. Nevertheless I do not see an error but a warning that system adminstrator should use for LSB/SysV boot scripts the LSB/SysV interface. I guess therefore that a bug report at the above site will not be successful but this is a guess only. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=852312 https://bugzilla.novell.com/show_bug.cgi?id=852312#c6 --- Comment #6 from Joerg Diederich 2013-11-29 13:30:42 UTC --- Just to clarify my point of view: "systemctl enable" works fine in opensuse 12.3 for old style init scripts as well without any annoying messages. In opensuse 13.1 you get these messages pretending making you think the command failed, which is, by the way, to true. This change in behaviour makes me think that systemctl is kind of broken in opensuse 13.1. Or put it the other way round: this is not a request for a new feature but to undo a change in upstream which makes things worse. For me as a normal user it's hard to decide who is to blame (the distributor or upstream). If nobody here can fix it then close this bug report. -- 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.