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 shutdown.target
Conflicts=shutdown.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`
dmeventd: ensure systemd service gets stopped on shutdown Add these for dmeventd systemd unit (dm-event.service): Before: shutdown.target Conflicts: shutdown.target This will cause the dmeventd to be properly stopped at shutdown (after all the dmeventd clients unregistered their devices from monitoring) with dm-event.service's stop action (there's no direct action defined for the "stop" so systemd sends SIGTERM instead). Before, we let dmeventd to get killed only as part of the very last SIGTERM/SIGKILL for all the remaining processes late in the shutdown sequence so we may have missed some logs if dmeventd encountered an error during its shutdown (logging facilities are already off at this late time in shutdown sequence). Ref: https://www.redhat.com/archives/lvm-devel/2017-October/msg00000.html 2017-10-05 13:52:15 +03:00			`Before=local-fs-pre.target shutdown.target`
			`Conflicts=shutdown.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`