Managing Serviceguard 14th Edition, June 2007

Cluster and Package Maintenance
Configuring a Legacy Package
Chapter 7366
NOTE For modular packages, the default form for parameter names in the
package configuration file is lower case; for legacy packages the
default is upper case. There are no compatibility issues;
Serviceguard is case-insensitive as far as the parameter names are
concerned.
Because this section is intended to be used primarily when you
reconfiguring an existing legacy package, we are using the legacy
parameter names (in upper case) for sake of continuity. But if you
generate the configuration file using cmmakepkg or cmgetconf, you
will see the parameter names as they appear in modular packages;
see the notes below and the “Package Parameter Explanations” on
page 281 for details of the name changes.
• FAILOVER_POLICY. For failover packages, enter the
failover_policy (see page 285).
• FAILBACK_POLICY. For failover packages, enter the
failback_policy (see page 286).
• NODE_NAME. Enter the node or nodes on which the package can run;
see node_name on page 282.
• AUTO_RUN. Configure the package to start up automatically or
manually; see auto_run on page 283.
• LOCAL_LAN_FAILOVER_ALLOWED. Enter the policy for
local_lan_failover_allowed (see page 288).
• NODE_FAIL_FAST_ENABLED. Enter the policy for
node_fail_fast_enabled (see page 283).
• RUN_SCRIPT and HALT_SCRIPT. Specify the pathname of the
package control script (described in the next section). No default is
provided. Permissions on the file and directory should be set to
rwxr-xr-x or r-xr-xr-x (755 or 555).
(Script timeouts): Enter the run_script_timeout (see page 283)
and halt_script_timeout (see page 284).
SCRIPT_LOG_FILE. (optional). Specify the full pathname of the file
where the RUN_SCRIPT and HALT_SCRIPT will log messages. If you do
not specify a path, Serviceguard will create a file with “.log”
appended to each script path, and put the messages in that file.