David Teigland 89deadf596 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 that may set up devices for PVs, like mulitpathd. These 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-10-12 10:50:43 -05:00
..
build.inc	spec: Remove unsupported config options	2018-07-24 15:00:12 +02:00
lvm2.spec	spec: Replace remaining %define by %global	2017-03-16 13:03:24 +01:00
macros.inc	rpm: bare words are no longer supported	2020-10-02 22:27:00 +02:00
packages.inc	add fixed event activation services	2021-10-12 10:50:43 -05:00
source.inc	spec: Enable integrity	2020-05-05 14:12:32 +02:00