Managing Serviceguard Sixteenth Edition, March 2009

These two parameters allow you to separate
package run instructions and package halt
instructions for legacy packages into separate
scripts if you need to. In this case, make sure you
include identical configuration information (such
as node names, IP addresses, etc.) in both scripts.
In most cases, though, HP recommends that you
use the same script for both run and halt
instructions. (When the package starts, the script
is passed the parameter start; when it halts, it is
passed the parameter stop.)
DEFERRED_RESOURCE_NAME Add DEFERRED_RESOURCE_NAME to a legacy
package control script for any resource that has
a RESOURCE_START setting of DEFERRED.
Generating the Package Configuration File
When you have chosen the configuration modules your package needs (see “Choosing
Package Modules” (page 254)), you are ready to generate a package configuration file
that contains those modules. This file will consist of a base module (usually failover,
multi-node or system multi-node) plus the modules that contain the additional
parameters you have decided to include.
Before You Start
Before you start building a package, create a subdirectory for it in the $SGCONF directory
(/etc/cmcluster); for example:
mkdir $SGCONF/pkg1
cmmakepkg Examples
The cmmakepkg command generates a package configuration file. Some examples
follow; see the cmmakepkg (1m) manpage for complete information. All the examples
create an editable configuration file pkg1.conf in the $SGCONF/pkg1 directory.
Generating the Package Configuration File 285