HP Serviceguard for Linux Version A.11.18 Release Notes, 2nd Edition, March 2009

The variable name must be in the form pev_<variable_name> and contain only
alphanumeric characters and underscores. The letters pev (upper-case or lower-case)
followed by the underscore (_) are required.
The variable name and value can each consist of a maximum of MAXPATHLEN
characters (4096 on Linux systems).
You can define more than one variable. For more information, see About External
Scripts” in Chapter 4 of Managing Serviceguard for Linux, and the comments in the
package configuration file.
external_pre_script
The full pathname of an external script to be executed before volume groups and disk
groups are activated during package startup, and after they have been deactivated
during package shutdown (that is, effectively the first step in package startup and last
step in package shutdown).
If more than one external_pre_script is specified, the scripts will be executed on package
startup in the order they are entered into this file, and in the reverse order during
package shutdown.
HP supplies a template for external scripts: $SGCONF/examples/
external_script.template.
For more information, see About External Scripts” in Chapter 4 of Managing
Serviceguard for Linux, and the comments in the package configuration file.
external_script
The full pathname of an external script. This script is often the means of launching and
halting the application that constitutes the main function of the package.
The script is executed on package startup after volume groups and file systems are
activated and IP addresses are assigned, but before services are started; and during
package shutdown after services are halted but before IP addresses are removed and
volume groups and file systems deactivated.
If more than one external_script is specified, the scripts will be executed on package
startup in the order they are entered into this file, and in the reverse order during
package shutdown.
HP supplies a template for external scripts: $SGCONF/examples/
external_script.template.
For more information, see About External Scripts” in Chapter 4 of Managing
Serviceguard for Linux, and the comments in the package configuration file.
Legacy and Modular Package-Configuration Parameters
There are some differences between the parameters used by modular packages and
the legacy parameters. Legacy parameters are still supported, but, as the following
What’s in this Release 25