lvm2/scripts/dm_event_systemd_red_hat.service.in

[Unit]
Description=Device-mapper event daemon
Documentation=man:dmeventd(8)
Requires=dm-event.socket
After=dm-event.socket
Before=local-fs-pre.target
DefaultDependencies=no

[Service]
Type=simple
ExecStart=@sbindir@/dmeventd -f
Environment=SD_ACTIVATION=1
PIDFile=@DMEVENTD_PIDFILE@
OOMScoreAdjust=-1000

[Install]
WantedBy=sysinit.target
Add systemd unit files for dmeventd. 2011-07-28 16:54:28 +04:00			`[Unit]`
			`Description=Device-mapper event daemon`
systemd: Add Documentation references These documentation references show up in "systemctl status" output. 2012-06-20 16:23:50 +04:00			`Documentation=man:dmeventd(8)`
Clean up systemd unit ordering and requirements. 2012-02-01 17:08:39 +04:00			`Requires=dm-event.socket`
			`After=dm-event.socket`
systemd: use {local,remote}-fs-pre.target instead of {local,remote}-fs.target We want most of our units to be started before any local/remote mount points are mounted - we used {local,remote}-fs.target for this purpose before, but it was not 100% correct as there's even {local,remote}-fs-pre.target special systemd unit reserved for this exact purpose. See also man 7 systemd.special and "local-fs-pre.target"/"remote-fs-pre.target" description. 2015-09-23 14:17:12 +03:00			`Before=local-fs-pre.target`
Add systemd unit files for dmeventd. 2011-07-28 16:54:28 +04:00			`DefaultDependencies=no`

			`[Service]`
dmeventd: fix dmeventd -R to work properly with systemd Trying to restart dmeventd as a reload action is causing problems under systemd environment. The systemd loses track of new dmeventd this way. See also https://bugzilla.redhat.com/show_bug.cgi?id=1060134 for more info. We need to call dmeventd -R directly instead of "systemctl reload dm-event.service" that was used before (the reload is aimed at configuration reload anyway, not stateful restart of the daemon - we did this before just because there's no ExecRestart in systemd and there's only ExecStart and ExecStop with which we'd lose the state). Also, use ExecStart="dmeventd -f" to run dmeventd in foreground (and let's rely on systemd to daemonize it) and change the service type from "forking" to "simple". 2014-02-03 19:07:06 +04:00			`Type=simple`
			`ExecStart=@sbindir@/dmeventd -f`
Use SD_ACTIVATION env. var. in systemd units to better detect systemd in use. LISTEN_PID and LISTEN_FDS environment variables are defined only during systemd "start" action. But we still need to know whether we're activated during "reload" action as well - we use the reload action to call "dmeventd -R"/"lvmetad -R" for statefull daemon restart. We can't use normal "restart" as that is simply composed of "stop" and "start" and we would lose any state the daemon has. 2012-03-14 19:51:51 +04:00			`Environment=SD_ACTIVATION=1`
Add systemd unit files for dmeventd. 2011-07-28 16:54:28 +04:00			`PIDFile=@DMEVENTD_PIDFILE@`
			`OOMScoreAdjust=-1000`

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