mirror of
git://sourceware.org/git/lvm2.git
synced 2024-10-28 11:55:55 +03:00
8a8abc5ed9
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".
18 lines
335 B
SYSTEMD
18 lines
335 B
SYSTEMD
[Unit]
|
|
Description=Device-mapper event daemon
|
|
Documentation=man:dmeventd(8)
|
|
Requires=dm-event.socket
|
|
After=dm-event.socket
|
|
Before=local-fs.target
|
|
DefaultDependencies=no
|
|
|
|
[Service]
|
|
Type=simple
|
|
ExecStart=@sbindir@/dmeventd -f
|
|
Environment=SD_ACTIVATION=1
|
|
PIDFile=@DMEVENTD_PIDFILE@
|
|
OOMScoreAdjust=-1000
|
|
|
|
[Install]
|
|
WantedBy=sysinit.target
|