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
Before=local-fs-pre.target shutdown.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 16:54:28 +04: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 16:23:50 +04: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 18:20:47 +03:00			`Requires=dm-event.socket`
remove static autoactivation event based autoactivation is now the only method that lvm provides for autoactivation. Setting lvm.conf event_activation=0 can still be used to disable event based autoactivation commands, but doing so will no longer enable static autoactivation. 2022-01-26 01:05:32 +03:00			`After=dm-event.socket dm-event.service`
systemd: add missing Before=shutdown.target to LVM2 services to fix shutdown ordering We already used Conflicts=shutdown target to stop LVM2 services on shutdown. But we still missed the ordering - the shutdown.target should be reached only after all the services are really stopped. Reported here: https://github.com/lvmteam/lvm2/issues/17 2019-04-09 13:10:17 +03:00			`Before=local-fs-pre.target shutdown.target`
Add systemd unit files for dmeventd. 2011-07-28 16:54:28 +04:00			`DefaultDependencies=no`
			`Conflicts=shutdown.target`

			`[Service]`
			`Type=oneshot`
Suppress locking error messages in monitoring init scripts. 2011-08-11 19:27:46 +04: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 23:43:59 +03:00			`ExecStart=@SBINDIR@/lvm vgchange --monitor y`
			`ExecStop=@SBINDIR@/lvm vgchange --monitor n`
Add systemd unit files for dmeventd. 2011-07-28 16:54:28 +04:00			`RemainAfterExit=yes`

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