Managing HP Serviceguard A.11.20.10 for Linux, December 2012

• If the package needs to mount LVM volumes to file systems (other than Red Hat GFS; see
fs_type (page 182)), use the vg parameters to specify the names of the volume groups to be
activated, and select the appropriate vgchange_cmd.
Use the fs_ parameters (page 181) to specify the characteristics of file systems and how and
where to mount them. See the comments in the FILESYSTEMS section of the configuration
file for more information and examples.
Enter each volume group on a separate line, for example:
vg vg01
vg vg02
• If your package mounts large number of file systems, consider increasing the values of the
following parameters:
◦ concurrent_fsck_operations—specifies the number of parallel fsck operations
that will be allowed at package startup (not used for Red Hat GFS).
Red Hat GFS is not supported in Serviceguard A.11.20.00.
• Specify the filesystem mount and unmount retry options. For Red Hat GFS (see fs_type
(page 182)), use the default (zero).
• You can use the pev_ parameter to specify a variable to be passed to external scripts. Make
sure the variable name begins with the upper-case or lower-case letters pev and an underscore
( _). You can specify more than one variable. See “About External Scripts” (page 122), and
the comments in the configuration file, for more information.
• If you want the package to run an external “pre-script” during startup and shutdown, use the
external_pre_script parameter (see (page 183)) to specify the full pathname of the script,
for example, $SGCONF/pkg1/pre_script1.
• If the package will run an external script, use the external_script parameter (see
(page 184)) to specify the full pathname of the script, for example, $SGCONF/pkg1/script1.
See “About External Scripts” (page 122), and the comments in the configuration file, for more
information.
• Configure the Access Control Policy for up to eight specific users or any_user.
The only user role you can configure in the package configuration file is package_admin
for the package in question. Cluster-wide roles are defined in the cluster configuration file.
See “Setting up Access-Control Policies” (page 154) for more information.
6.4 Verifying and Applying the Package Configuration
Serviceguard checks the configuration you enter and reports any errors.
Use a command such as the following to verify the content of the package configuration file you
have created, for example:
cmcheckconf -v -P $SGCONF/pkg1/pkg1.conf
Errors are displayed on the standard output. If necessary, re-edit the file to correct any errors, then
run cmcheckconf again until it completes without errors.
The following items are checked:
• Package name is valid, and at least one node_name entry is included.
• There are no duplicate parameter entries (except as permitted for multiple volume groups,
etc).
• Values for all parameters are within permitted ranges.
6.4 Verifying and Applying the Package Configuration 189