Bug 72154

Summary:	"systemctl enable named.service" yields error messages used for legacy sysinit scripts
Product:	systemd	Reporter:	joerg_diederich
Component:	general	Assignee:	systemd-bugs
Status:	RESOLVED FIXED	QA Contact:	systemd-bugs
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description joerg_diederich 2013-11-29 13:51:23 UTC

When I try to enable the named service using the command "systemctl enable
named.service" I get the error message:
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, ...).

In systemd version 195 this works fine without these messages. I have already opened a bug for opensuse 13.1. But the guys there told me to open a bug in upstream instead.

Bug report for opensuse 13.1:
https://bugzilla.novell.com/show_bug.cgi?id=852312

Comment 1 Lennart Poettering 2014-02-21 14:23:40 UTC

Let me get this right:

named is a sysv service, it does not have a native unit file? And if you try to enable it with "systemctl enable" then you will get the blurb that it has no [Install] section? If that's the case this would indeed be a bug.

Can you test with 209 and see if the problem persists?

Comment 2 joerg_diederich 2014-03-03 18:45:56 UTC

Your summary of the problem is correct: enabling a legacy sysv service which has no systemd service configuration (like named in opensuse 13.1) yields the error messages. 

Today I tested again with version 209 as suggested. With this version it works fine without error messages.

Comment 3 Lennart Poettering 2014-03-03 18:58:17 UTC

OK, if it works with current versions, let's close the bug.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.