Managing Serviceguard Eighteenth Edition, September 2010

• If your package uses a large number of volume groups or disk groups, or mounts
a large number of file systems, consider increasing the values of the following
parameters:
— concurrent_vgchange_operations (page 302)
— concurrent_fsck_operations (page 306)
— concurrent_mount_and_umount_operations (page 306)
You can also use the fsck_opt and fs_umount_opt parameters (page 309) to specify
the -s option of the fsck and mount/umount commands.
• You can use the pev_ parameter (page 309) 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 197), and the comments in the
configuration file, for more details.
• If you want the package to run an external “pre-script” during startup and
shutdown, use the external_pre_script parameter (see (page 309)) to specify the full
pathname of the script, for example /etc/cmcluster/pkg1/pre_script1.
• If the package will run an external script, use the external_script parameter (see
(page 309)) to specify the full pathname of the script, for example /etc/
cmcluster/pkg1/script1.
See “About External Scripts” (page 197), and the comments in the configuration
file, for more information.
• To coordinate the startup and shutdown of database software with cluster node
startup and shutdown, you can use the database template files provided with the
separately purchasable Enterprise Cluster Master Toolkit product.
These files are in /opt/cmcluster/toolkit/DB/. Separate toolkits are available
for Oracle, Informix, and Sybase.
In addition to the standard package script, you use the special script that is provided
for the database. To set up these scripts, follow the instructions in the README
file provided with each toolkit.
• 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 254)
for more information.
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:
Verifying and Applying the Package Configuration 317