RepoMirrors
/
selinux
mirror of https://github.com/SELinuxProject/selinux
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
selinux/restorecond/restorecond.service

13 lines
259 B
SYSTEMD
Raw Normal View History

Add support for systemd service for restorecond
2013-10-09 21:36:36 +00:00
[Unit]
Description=Restorecon maintaining path file context
ConditionPathExists=/etc/selinux/restorecond.conf
Improve restorecond systemd unit file Use Type=forking and pass PIDFile option, this allows better tracking of the livecycle of the daemon. Only attempt to start the daemon if selinux is enabled. Drop After=syslog.target, syslog is socket activated anyway
2013-11-06 12:24:00 +00:00
ConditionSecurity=selinux
Add support for systemd service for restorecond
2013-10-09 21:36:36 +00:00
[Service]
Improve restorecond systemd unit file Use Type=forking and pass PIDFile option, this allows better tracking of the livecycle of the daemon. Only attempt to start the daemon if selinux is enabled. Drop After=syslog.target, syslog is socket activated anyway
2013-11-06 12:24:00 +00:00
Type=forking
Add support for systemd service for restorecond
2013-10-09 21:36:36 +00:00
ExecStart=/usr/sbin/restorecond
restorecond: use /run instead of /var/run On most distributions, /var/run is a symbolic link to /run so using /var/run or /run lead to the same result. Nevertheless systemd started to warn about using /var/run in a service file, logging entries such as: /usr/lib/systemd/system/restorecond.service:8: PIDFile= references path below legacy directory /var/run/, updating /var/run/restorecond.pid → /run/restorecond.pid; please update the unit file accordingly. Switch to /run in order to follow this advice. Signed-off-by: Nicolas Iooss <nicolas.iooss@m4x.org>
2019-02-26 19:02:07 +00:00
PIDFile=/run/restorecond.pid
Add support for systemd service for restorecond
2013-10-09 21:36:36 +00:00
[Install]
WantedBy=multi-user.target