Managing HP Serviceguard for Linux, Sixth Edition, August 2006

Configuring Packages and Their Services
Writing the Package Control Script
Chapter 6 189
Customizing the Package Control Script
Check the definitions and declarations at the beginning of the control
script using the information in the Package Configuration worksheet.
For more information see “Understanding the Location of Serviceguard
Files” on page 122. You need to customize as follows:
• Update the PATH statement to reflect any required paths needed to
start your services.
• Enter the names of LVM volume groups that will be activated.
• Add the names of LVM logical volumes and file systems that will be
mounted on them. Specify the file system type (ext2 is the default;
ext3 or reiserfs can also be used.).
• Define IP subnet and IP address pairs for your package.
• Add service name(s).
• Add service command(s).
• Add a service restart parameter, if desired.
NOTE Use care in defining service run commands. Each run command is
executed by the control script in the following way:
•The cmrunserv command executes each run command and then
monitors the process id of the process created by the run command.
• When the command started by cmrunserv exits, Serviceguard
determines that a failure has occurred and takes appropriate action,
which may include transferring the package to an adoptive node.
• If a run command is a shell script that runs some other command
and then exits, Serviceguard will consider this normal exit as a
failure.
To avoid problems in the execution of control scripts, ensure that each
run command is the name of an actual service and that its process
remains alive until the actual service stops.
If you need to define a set of run and halt operations in addition to the
defaults, create functions for them in the sections under the heading
CUSTOMER DEFINED FUNCTIONS.