* Does the service require post-rpm-installation configuration in order to be useful (for example, does it need manual edits to a configuration file)?

No

* Does the service listen on a network socket for connections originating on a separate physical or virtual machine?

No

* Is the service non-persistent (i.e. run once at startup and exit)?

Yes

* What is the exact name (or names) of the systemd unit files to be enabled?

selinux-autorelabel-mark.service

* Is this request for all Fedora deliverables or only for some Editions (list them)?

All



The current situation is that selinux-autorelabel-mark.service services is enabled via symlink shipped in policycoreutils package:

ln -s ../selinux-autorelabel-mark.service %{buildroot}/%{_unitdir}/basic.target.wants/


When this request is resolved, we'll change the service to use:

[Install]
WantedBy=sysinit.target

and policycoreutils.spec file to use:

%post
%systemd_post selinux-autorelabel-mark.service

%preun
%systemd_preun selinux-autorelabel-mark.service



This is based on the initscripts change which happened in rhel7-branch - https://github.com/fedora-sysv/initscripts/commit/995e8ad74f5a6bc51f28c0be4ed02c547e0891d6