lvm2/scripts/lvm2_cmirrord_systemd_red_hat.service.in

[Unit]
Description=Clustered LVM mirror log daemon
Documentation=man:cmirrord(8)
Requires=corosync.service
After=corosync.service
Before=remote-fs-pre.target
DefaultDependencies=no
Conflicts=shutdown.target

[Service]
Type=forking
ExecStart=@sbindir@/cmirrord
PIDFile=@CMIRRORD_PIDFILE@
Restart=on-abort

[Install]
WantedBy=multi-user.target
systemd: add systemd unit for cmirrord 2014-02-11 12:55:57 +04:00			`[Unit]`
			`Description=Clustered LVM mirror log daemon`
			`Documentation=man:cmirrord(8)`
			`Requires=corosync.service`
			`After=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`
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`
systemd: add systemd unit for cmirrord 2014-02-11 12:55:57 +04:00
			`[Service]`
			`Type=forking`
revert: 7639eae and 4a52a92 Revert 7639eae8919e5872143562db8118d039f5a41225 and 4a52a9212cc5d3ae90196776f28dbfb319002c74. We need a better fix here. 2014-11-20 10:22:34 +03:00			`ExecStart=@sbindir@/cmirrord`
systemd: add systemd unit for cmirrord 2014-02-11 12:55:57 +04:00			`PIDFile=@CMIRRORD_PIDFILE@`
			`Restart=on-abort`

			`[Install]`
			`WantedBy=multi-user.target`