From 9cdd4dcca7e6d166e44270a81425a50e598836f4 Mon Sep 17 00:00:00 2001 From: Zdenek Kabelac Date: Thu, 22 Apr 2021 11:28:56 +0200 Subject: make: generate --- conf/example.conf.in | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) (limited to 'conf') diff --git a/conf/example.conf.in b/conf/example.conf.in index 19efe6b6d..b4a55ae6a 100644 --- a/conf/example.conf.in +++ b/conf/example.conf.in @@ -1084,13 +1084,14 @@ global { # Configuration option global/event_activation. # Activate LVs based on system-generated device events. - # When a device appears on the system, a system-generated event runs - # the pvscan command to activate LVs if the new PV completes the VG. - # When event_activation is disabled, the system will generally run - # a direct activation command to activate LVs in complete VGs. - # Activation commands that are run by the system, either from events - # or at fixed points during startup, use autoactivation (-aay). See - # the --setautoactivation option or the auto_activation_volume_list + # When a PV appears on the system, a system-generated uevent triggers + # the lvm2-pvscan service which runs the pvscan --cache -aay command. + # If the new PV completes a VG, pvscan autoactivates LVs in the VG. + # When event_activation is disabled, the lvm2-activation services are + # generated and run at fixed points during system startup. These + # services run vgchange -aay to autoactivate LVs in VGs that happen + # to be present at that point in time. + # See the --setautoactivation option or the auto_activation_volume_list # setting to configure autoactivation for specific VGs or LVs. # This configuration option has an automatic default value. # event_activation = 1 -- cgit v1.2.1