shaba/lvm2
1
0
Fork 0
mirror of git://sourceware.org/git/lvm2.git synced 2024-12-22 17:35:59 +03:00
Code Releases Activity
2a22576b2d
lvm2/scripts/lvm2_clvmd_systemd_red_hat.service.in

24 lines
557 B
SYSTEMD
Raw Normal View History

Add systemd native service for clvmd and cluster activation The commit splits original clvmd service in two new native services for systemd enabled systems while original init scripts remain unaltered. New systemd native services: 1) clvmd daemon itself (lvm2_clvmd_red_hat.service.in) 2) (de)activation of clustered VGs (lvm2_cluster_activation_red_hat.service.in) There're several reasons to split it. First, there's no support for conditional stop in systemd and AFAIK they don't plan to support it. In other words: if the deactivation fails for some reason, systemd doesn't care and will simply kill all remaining processes in original cgroup (by default). Killing the remaining procs can be suppressed however it doesn't solve the following problem: You can't repeat the stop command of a failed service. The repeated stop command is simply not propagated to the service in a failed state. You would have to start and then try to stop the service again. Unfortunately, this can't be done while the daemon is still running (and we need the daemon to stay active until all clustered VGs are deactivated properly). In a separated setup we need only to restart the failed activation service and that's fine.
2014-02-10 20:05:10 +04:00
[Unit]
Description=Clustered LVM daemon
Documentation=man:clvmd(8)
After=dlm.service corosync.service
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=remote-fs-pre.target
Add systemd native service for clvmd and cluster activation The commit splits original clvmd service in two new native services for systemd enabled systems while original init scripts remain unaltered. New systemd native services: 1) clvmd daemon itself (lvm2_clvmd_red_hat.service.in) 2) (de)activation of clustered VGs (lvm2_cluster_activation_red_hat.service.in) There're several reasons to split it. First, there's no support for conditional stop in systemd and AFAIK they don't plan to support it. In other words: if the deactivation fails for some reason, systemd doesn't care and will simply kill all remaining processes in original cgroup (by default). Killing the remaining procs can be suppressed however it doesn't solve the following problem: You can't repeat the stop command of a failed service. The repeated stop command is simply not propagated to the service in a failed state. You would have to start and then try to stop the service again. Unfortunately, this can't be done while the daemon is still running (and we need the daemon to stay active until all clustered VGs are deactivated properly). In a separated setup we need only to restart the failed activation service and that's fine.
2014-02-10 20:05:10 +04:00
Requires=network.target dlm.service corosync.service
RefuseManualStart=true
RefuseManualStop=true
StopWhenUnneeded=true
systemd: do not use default dependencies for clvmd/cmirrord units Do not use default dependencies that systemd adds to the units so we have better control of when the service is started/stopped and we don't end up with unexpected behaviour.
2014-02-14 17:37:19 +04:00
DefaultDependencies=no
Conflicts=shutdown.target
Add systemd native service for clvmd and cluster activation The commit splits original clvmd service in two new native services for systemd enabled systems while original init scripts remain unaltered. New systemd native services: 1) clvmd daemon itself (lvm2_clvmd_red_hat.service.in) 2) (de)activation of clustered VGs (lvm2_cluster_activation_red_hat.service.in) There're several reasons to split it. First, there's no support for conditional stop in systemd and AFAIK they don't plan to support it. In other words: if the deactivation fails for some reason, systemd doesn't care and will simply kill all remaining processes in original cgroup (by default). Killing the remaining procs can be suppressed however it doesn't solve the following problem: You can't repeat the stop command of a failed service. The repeated stop command is simply not propagated to the service in a failed state. You would have to start and then try to stop the service again. Unfortunately, this can't be done while the daemon is still running (and we need the daemon to stay active until all clustered VGs are deactivated properly). In a separated setup we need only to restart the failed activation service and that's fine.
2014-02-10 20:05:10 +04:00
[Service]
Type=forking
Environment=CLVMD_OPTS=-T30
systemd: use proper sbindir path Replace lowercase @sbindir@ with @SBINDIR@ which contains fully decoded path. Same with @usrsbindir@ which is also used with clvmd and cmirrord. Also handle SYSCONFDIR for EnvironmentFile. Patch fixes generated unit files with strings like: ExecStart=${exec_prefix}/sbin/lvm
2017-10-25 18:06:41 +03:00
EnvironmentFile=-@SYSCONFDIR@/sysconfig/clvmd
ExecStart=@USRSBINDIR@/clvmd $CLVMD_OPTS
Add systemd native service for clvmd and cluster activation The commit splits original clvmd service in two new native services for systemd enabled systems while original init scripts remain unaltered. New systemd native services: 1) clvmd daemon itself (lvm2_clvmd_red_hat.service.in) 2) (de)activation of clustered VGs (lvm2_cluster_activation_red_hat.service.in) There're several reasons to split it. First, there's no support for conditional stop in systemd and AFAIK they don't plan to support it. In other words: if the deactivation fails for some reason, systemd doesn't care and will simply kill all remaining processes in original cgroup (by default). Killing the remaining procs can be suppressed however it doesn't solve the following problem: You can't repeat the stop command of a failed service. The repeated stop command is simply not propagated to the service in a failed state. You would have to start and then try to stop the service again. Unfortunately, this can't be done while the daemon is still running (and we need the daemon to stay active until all clustered VGs are deactivated properly). In a separated setup we need only to restart the failed activation service and that's fine.
2014-02-10 20:05:10 +04:00
SuccessExitStatus=5
TimeoutStartSec=30
TimeoutStopSec=10
OOMScoreAdjust=-1000
Restart=on-abort
PIDFile=@CLVMD_PIDFILE@
Copy Permalink