Bug 1090684 (autoenabled-systemd-units) - rpm scripts and triggers should not enable systemd units directly
Summary: rpm scripts and triggers should not enable systemd units directly
Status: NEW
Alias: autoenabled-systemd-units
Product: Fedora
Classification: Fedora
Component: distribution
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Václav Pavlín
QA Contact: Fedora Extras Quality Assurance
Depends On: 850058 850186 1087950 1087951 1089650 1094894 1094895 1094896 1094897 1094898 1094899 1094900 1094901 1094902 1094903 1094904 1094906 1094907 1094908 1094909 1094910 1094911 1094912 1094913 1094914 1094915 1094916 1094917 1094918 1094919 1094920 1094921 1094922 1094927 1094928 1094929 1094930 1094931 1094932 1094933 1094934 1094935 1094936 1094938 1163968 1271839
TreeView+ depends on / blocked
Reported: 2014-04-23 23:48 UTC by Andy Lutomirski
Modified: 2017-02-07 11:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed:
Type: Bug

Attachments (Terms of Use)

Description Andy Lutomirski 2014-04-23 23:48:58 UTC
A number of packages install systemd units and enable them
automatically.  They should not.  Please update these packages to use the
macroized scriptlet

If your package has an exception from FESCo permitting it to enable
itself, please make sure that the service in question is listed in the
appropriate preset file.

There is a general exception described here:


If your package falls under the general exception, then it is possible
that no change is required.  Nevertheless, if you are relying on the
exception, please make sure that your rpm scripts are sensible.  The
exception is:

In addition, any service which does not remain persistent on the system (aka, it "runs once then goes away"), does not listen to incoming connections during initialization, and does not require configuration to be functional may be enabled by default (but is not required to do so). An example of "runs once then goes away" service is iptables.

Given that this issue can affect Fedora 20 users who install your
package as a dependency, these bugs should be fixed in Fedora 20 and

Note You need to log in before you can comment on or make changes to this bug.