HP Serviceguard Developer's Toolbox Version B.12.00.00 For HP-UX and Linux

# Volume Group Activation
#
# "vgchange_cmd" is the method of activation for LVM volume groups.
#
# Specify the method of activation for volume groups.
# Leave the default ("vgchange_cmd "vgchange -a y") if you want volume
# groups activated in default mode.
#
# "vgchange_cmd" replaces the legacy package control script parameter "vgchange".
#
# Legal values for vgchange_cmd: <Any String>
vgchange_cmd "vgchange -a y"
# Volume Groups
#
# "vg" is used to specify which volume groups are used by this package.
#
# Specify the name of each volume group.
#
# For example, if this package uses your volume groups vg01 and vg02, enter:
# vg vg01
# vg vg02
#
# The volume groups must not be set if the underlying file system is GFS.
#
# The volume group activation method is defined above. The filesystems
# associated with these volume groups are specified below.
#
# Legal values for vg: /^[0-9A-Za-z\/][0-9A-Za-z_.\/\-]*[0-9A-Za-z]$/, /^[0-9A-Za-z]$/. vg mysql_vg
# "concurrent_fsck_operations" specifies the number of concurrent fsck
# operations.
#
# FILESYSTEMS
#
# Filesystems are defined by entries specifying the logical volume, the
# mount point, the options for mount, umount and fsck, and the type of the file system.
# Each filesystem will be fsck'd prior to being mounted. The filesystems
# will be mounted in the order specified during package startup and will
# be unmounted in reverse order during package shutdown. Ensure that
# volume groups referenced by the logical volume definitions below are
# included in volume group definitions ("vg") above.
#
# concurrent_fsck_operations
#
# Specify the number of concurrent fsck operations to allow during
# package startup.
# Setting this value to an appropriate number may improve performance if
# a large number of file systems need to be checked. The default is 1.
# This attribute is ignored, if the underlying file system is Red Hat
# GFS, since fsck operations will not be performed in case of GFS.
#
# Legal values for concurrent_fsck_operations: (value > 0). concurrent_fsck_operations 1
# "concurrent_mount_and_umount_operations" specifies the number of concurrent
# mounts and umounts to allow during package startup and shutdown..
#
# Setting this value to an appropriate number may improve the performance
# if the package needs to mount and un-mount a large number of file systems.
# The default is 1.
#
# Legal values for concurrent_mount_and_umount_operations: (value > 0). concurrent_mount_and_umount_operations
1
# "fs_mount_retry_count" specifies the number of mount retries.
#
# The default is 0. During startup, if a mount point is busy
# and "fs_mount_retry_count" is 0, package startup will fail and
# the script will exit with 1. If a mount point is busy and
# "fs_mount_retry_count" is greater than 0, the script will attempt
# to kill the user process responsible for the busy mount point
# ("fuser -ku") and then mount the file system. It will do this
# the number of times specified in "fs_mount_retry_count".
# If the mount still fails after this number of attempts, the script
# will exit with 1.
#
# fs_mount_retry_count must be set to zero (default), if the underlying
# file system is of type Red Hat GFS.
#
# Legal values for fs_mount_retry_count: (value >= 0). fs_mount_retry_count 0
# "fs_umount_retry_count" specifies the number of unmount retries for each filesystem during package shutdown.
#
# The default is set to 1. During package halt time, if a mount point
# is busy the script will attempt to kill the user responsible for the
# busy mount point and then umount the file system. It will attempt to
# kill user and retry umount, for the number of times specified in
# "fs_umount_retry_count". If the umount still fails after this number
# of attempts, the script will exit with 1.
#
#
# NOTE: The script will execute "fuser -ku" to free up busy mount point by
# default.
24 MySQL Toolkit scripts