Managing Serviceguard Eighteenth Edition, September 2010

NOTE: If you set concurrent_vgchange_operations to a value greater than 1, you may
see messages such as this in the package log file:
Cannot lock “/etc/lvmconf//lvm_lock” still trying...”
This is an informational message that can be safely ignored.
enable_threaded_vgchange
Indicates whether multi-threaded activation of volume groups (vgchange -T)is
enabled. New for modular packages. Available on HP-UX 11i v3 only.
Legal values are zero (disabled) or 1 (enabled). The default is zero.
Set enable_threaded_vgchange to 1 to enable vgchange -T for all of a package’s volume
groups. This means that when each volume group is activated, physical volumes (disks
or LUNs) are attached to the volume group in parallel, and mirror copies of logical
volumes are synchronized in parallel, rather than serially. That can improve a package’s
startup performance if its volume groups contain a large number of physical volumes.
Note that, in the context of a Serviceguard package, this affects the way physical volumes
are activated within a volume group; concurrent_vgchange_operations (page 302) controls
how many volume groups the package can activate simultaneously.
IMPORTANT: Make sure you read the configuration file comments for both
concurrent_vgchange_operations and enable_threaded_vgchange before configuring these
options, as well as the vgchange (1m) manpage.
vgchange_cmd
Specifies the method of activation for each HP-UX Logical Volume Manager (LVM)
volume group identified by a vg entry (see (page 304)). Replaces VGCHANGE which
is still supported in the package control script for legacy packages; see “Configuring
a Legacy Package” (page 375).
The default is vgchange -a e.
The configuration file contains several other vgchange command variants; either
uncomment one of these and comment out the default, or use the default. For more
information, see the explanations in the configuration file, “LVM Planning ” (page 132),
and “Creating the Storage Infrastructure and Filesystems with LVM, VxVM and CVM”
(page 230).
Choosing Package Modules 303