diff options
| author | Peter Rajnoha <prajnoha@redhat.com> | 2011-10-31 12:22:49 +0000 |
|---|---|---|
| committer | Peter Rajnoha <prajnoha@redhat.com> | 2011-10-31 12:22:49 +0000 |
| commit | 8626490ca7d79252406d58ecf0f84eedee926087 (patch) | |
| tree | cd20a21fb49e571b890ec81b81b63093329ce271 /scripts/dm_event_systemd_red_hat.service.in | |
| parent | 25de9addb687122236b7850b1e094b96ebea572c (diff) | |
| download | lvm2-8626490ca7d79252406d58ecf0f84eedee926087.tar.gz | |
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.
Diffstat (limited to 'scripts/dm_event_systemd_red_hat.service.in')
| -rw-r--r-- | scripts/dm_event_systemd_red_hat.service.in | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/scripts/dm_event_systemd_red_hat.service.in b/scripts/dm_event_systemd_red_hat.service.in index 32295d3a0..4669ab809 100644 --- a/scripts/dm_event_systemd_red_hat.service.in +++ b/scripts/dm_event_systemd_red_hat.service.in @@ -7,6 +7,7 @@ DefaultDependencies=no [Service] Type=forking ExecStart=@sbindir@/dmeventd +ExecReload=@sbindir@/dmeventd -R PIDFile=@DMEVENTD_PIDFILE@ OOMScoreAdjust=-1000 |