Managing Serviceguard 14th Edition, June 2007

Cluster and Package Maintenance
Configuring a Legacy Package
Chapter 7370
Do not include CFS-based disk groups in the package control script;
on systems that support CFS and CVM, they are activated by the
CFS multi-node packages before standard packages are started.
• If you are using mirrored VxVM disks, specify the mirror recovery
option VXVOL.
• Add the names of logical volumes and the file system that will be
mounted on them.
• Select the appropriate options for the storage activation command
(not applicable for basic VxVM disk groups), and also include options
for mounting filesystems, if desired.
• Specify the filesystem mount and unmount retry options.
• If your package uses a large number of volume groups or disk groups
or mounts a large number of file systems, consider increasing the
number of concurrent vgchange, mount/umount, and fsck operations;
• Define IP subnet and IP address pairs for your package. IPv4 or IPv6
addresses may be used.
• Add service name(s).
• Add service command(s)
• Add a service restart parameter, if you so decide.
For more information about services, see the discussion of the
service_ parameters that starts on page 289.
• Specify whether or not to kill processes accessing raw devices; see the
comments in the file under RAW DEVICES for more information.
Adding Customer Defined Functions to the Package Control
Script
You can add additional shell commands to the package control script to
be executed whenever the package starts or stops. Enter these
commands in the CUSTOMER DEFINED FUNCTIONS area of the script.
If your package needs to run short-lived processes, such as commands to
initialize or halt a packaged application, you can also run these from the
CUSTOMER DEFINED FUNCTIONS.
An example of this portion of the script follows, showing the date and
echo commands logging starts and halts of the package to a file.