lvm2/scripts/lvm2_monitoring_systemd_red_hat.service.in

[Unit]
Description=Monitor LVM Logical Volumes
Documentation=man:dmeventd(8) man:lvcreate(8) man:lvchange(8) man:vgchange(8)
Requires=dm-event.socket
After=dm-event.socket dm-event.service lvm-activate-vgs-last.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]`
add fixed event activation services Add two new fixed activation services for startup: lvm-activate-vgs-main and lvm-activate-vgs-last. The -main service runs early, without service dependencies. The -last service runs later, after other services have started (other services that may set up devices for PVs, like mulitpathd.) The lvm-activate-vgs services both run "vgchange -aay" to activate all VGs that are preset and complete at the time of system startup. When there are many VGs, these two vgchange commands will replace many per-VG vgchange commands. The last service enables event activation by creating the file /run/lvm/event-activation-on. After that, new devices that appear will be processed by event based autoactivation commands. Prior to the existence of the event-activation-on file, event-based commands do nothing. lvm.conf event_activation_options can be used to configure service-based activation only, or event-based activation only, or the approach described above which begins with service based activation and then switches to event-based. service_only: only the -main and -last services will activate VGs. VGs on devices that appear later will not be autoactivated. event_only: the -main and -last services will not activate any VGs, and all VGs will be activated from per-VG event-based activation commands. service_to_event: the -main and -last services will activate VGs that are complete at the time the services run, and VGs that appear later will be activated from per-VG event-based activation commands. 2021-09-03 00:55:04 +03:00			`Description=Monitor LVM Logical Volumes`
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`
add fixed event activation services Add two new fixed activation services for startup: lvm-activate-vgs-main and lvm-activate-vgs-last. The -main service runs early, without service dependencies. The -last service runs later, after other services have started (other services that may set up devices for PVs, like mulitpathd.) The lvm-activate-vgs services both run "vgchange -aay" to activate all VGs that are preset and complete at the time of system startup. When there are many VGs, these two vgchange commands will replace many per-VG vgchange commands. The last service enables event activation by creating the file /run/lvm/event-activation-on. After that, new devices that appear will be processed by event based autoactivation commands. Prior to the existence of the event-activation-on file, event-based commands do nothing. lvm.conf event_activation_options can be used to configure service-based activation only, or event-based activation only, or the approach described above which begins with service based activation and then switches to event-based. service_only: only the -main and -last services will activate VGs. VGs on devices that appear later will not be autoactivated. event_only: the -main and -last services will not activate any VGs, and all VGs will be activated from per-VG event-based activation commands. service_to_event: the -main and -last services will activate VGs that are complete at the time the services run, and VGs that appear later will be activated from per-VG event-based activation commands. 2021-09-03 00:55:04 +03:00			`After=dm-event.socket dm-event.service lvm-activate-vgs-last.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`