Managing Serviceguard Eighteenth Edition, September 2010

Additional Parameters Used Only by Legacy Packages
IMPORTANT: The following parameters are used only by legacy packages. Do not
try to use them in modular packages. See “Configuring a Legacy Package” (page 375)
for more information.
PATH Specifies the path to be used by the script.
SUBNET Specifies the IP subnets that are to be monitored
for the package.
RUN_SCRIPT and HALT_SCRIPT Use the full pathname of each script.
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 280)), 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
Generating the Package Configuration File 311