lvm2/scripts/dm_event_systemd_red_hat.service.in

[Unit]
Description=Device-mapper event daemon
Requires=dm-event.socket
After=dm-event.socket
Before=local-fs.target
DefaultDependencies=no

[Service]
Type=forking
ExecStart=@sbindir@/dmeventd
ExecReload=@sbindir@/dmeventd -R
PIDFile=@DMEVENTD_PIDFILE@
OOMScoreAdjust=-1000

[Install]
WantedBy=sysinit.target
Add systemd unit files for dmeventd. 2011-07-28 12:54:28 +00:00			`[Unit]`
			`Description=Device-mapper event daemon`
Clean up systemd unit ordering and requirements. 2012-02-01 13:08:39 +00:00			`Requires=dm-event.socket`
			`After=dm-event.socket`
Add systemd unit files for dmeventd. 2011-07-28 12:54:28 +00:00			`Before=local-fs.target`
			`DefaultDependencies=no`

			`[Service]`
			`Type=forking`
			`ExecStart=@sbindir@/dmeventd`
Add "ExecReload" to dm-event.service for systemd to reload dmeventd properly. Normally, restart simply means "stop and start" for systemd. However, if we're installing new versions of the dmeventd binary/libdevmapper, we need to restart dmeventd. This fails if we have some devices monitored - we need to call "dmeventd -R" instead. The "ExecReload" did not work quite well in some old versions of systemd, systemd assumed that only the configuration is reloaded on "ExecReload", not the whole binary itself so it lost track of dmeventd daemon (it lost new dmeventd PID). This is fixed and seems to be working fine now with recent versions of dmeventd. 2011-10-31 12:22:49 +00:00			`ExecReload=@sbindir@/dmeventd -R`
Add systemd unit files for dmeventd. 2011-07-28 12:54:28 +00:00			`PIDFile=@DMEVENTD_PIDFILE@`
			`OOMScoreAdjust=-1000`

			`[Install]`
			`WantedBy=sysinit.target`