Bug 980045 - Avoid passing unit templates to systemctl
Summary: Avoid passing unit templates to systemctl
Status: NEW
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Current
Hardware: All Linux
: P5 - None : Enhancement (vote)
Target Milestone: ---
Assignee: Jan Engelhardt
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-14 15:34 UTC by Jan Engelhardt
Modified: 2016-05-14 15:34 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Engelhardt 2016-05-14 15:34:26 UTC 
# zypper in 389-ds
Retrieving: 389-ds-1.3.4.8-1.3.x86_64.rpm ................................[done]
Checking for file conflicts: .............................................[done]
(1/1) Installing: 389-ds-1.3.4.8-1.3.x86_64 ..............................[done]
Additional rpm output:
Updating /etc/sysconfig/dirsrv ...
Updating /etc/sysconfig/dirsrv.systemd ...
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, ...).


The warning arises because the package called `systemctl preset whatever@.service`. preset/enable/start/stop/etc. is not defined for templates; only the "disable" action is, so template files should only be passed to %systemd_del_preun at this point.