lvm2/scripts/lvm2_monitoring_systemd_red_hat.service.in

[Unit]
Description=Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling
Documentation=man:dmeventd(8) man:lvcreate(8) man:lvchange(8) man:vgchange(8)
Requires=dm-event.socket
After=dm-event.socket dm-event.service lvm2-activation.service
Before=local-fs-pre.target
DefaultDependencies=no
Conflicts=shutdown.target

[Service]
Type=oneshot
Environment=LVM_SUPPRESS_LOCKING_FAILURE_MESSAGES=1
ExecStart=@SBINDIR@/lvm vgchange --monitor y
ExecStop=@SBINDIR@/lvm vgchange --monitor n
RemainAfterExit=yes

[Install]
WantedBy=sysinit.target
Add systemd unit files for dmeventd. 2011-07-28 12:54:28 +00:00			`[Unit]`
			`Description=Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling`
systemd: Add Documentation references These documentation references show up in "systemctl status" output. 2012-06-20 14:23:50 +02:00			`Documentation=man:dmeventd(8) man:lvcreate(8) man:lvchange(8) man:vgchange(8)`
lvm2-monitoring service shouldn't refer to lvmetad 2018-11-15 09:20:47 -06:00			`Requires=dm-event.socket`
			`After=dm-event.socket dm-event.service lvm2-activation.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 13:17:12 +02:00			`Before=local-fs-pre.target`
Add systemd unit files for dmeventd. 2011-07-28 12:54:28 +00:00			`DefaultDependencies=no`
			`Conflicts=shutdown.target`

			`[Service]`
			`Type=oneshot`
Suppress locking error messages in monitoring init scripts. 2011-08-11 15:27:46 +00:00			`Environment=LVM_SUPPRESS_LOCKING_FAILURE_MESSAGES=1`
Drop --ignoreskippedcluster option It's no longer needed. Clustered VGs are now handled in the same way as foreign VGs, and as shared VGs that can't be accessed: - A command processing all VGs sees a clustered VG, prints a message ("Skipping clustered VG foo."), skips it, and does not fail. - A command where the clustered VG is explicitly named on the command line, prints a message and fails. "Cannot access clustered VG foo, see lvmlockd(8)." The option is listed in the set of ignored options for the commands that previously accepted it. (Removing it entirely would cause commands/scripts to fail if they set it.) 2018-06-15 15:43:59 -05:00			`ExecStart=@SBINDIR@/lvm vgchange --monitor y`
			`ExecStop=@SBINDIR@/lvm vgchange --monitor n`
Add systemd unit files for dmeventd. 2011-07-28 12:54:28 +00:00			`RemainAfterExit=yes`

			`[Install]`
			`WantedBy=sysinit.target`