Managing HP Serviceguard A.11.20.10 for Linux, December 2012

3.4.3 During Run Script Execution
Once the package manager has determined that the package can start on a particular node, it
launches the script that starts the package (that is, a package’s control script or master control
script is executed with the start parameter). This script carries out the following steps:
1. Executes any external_pre_scripts (modular packages only; see “About External Scripts”
(page 122))
2. Activates volume groups or disk groups.
3. Mounts file systems.
4. Assigns package IP addresses to the LAN card on the node (failover packages only).
5. Executes any customer-defined run commands (legacy packages only; see “Adding Customer
Defined Functions to the Package Control Script ” (page 228)) or external_scripts (modular
packages only; see “About External Scripts” (page 122)).
6. Starts each package service.
7. Exits with an exit code of zero (0).
Figure 20 Legacy Package Time Line
At any step along the way, an error will result in the script exiting abnormally (with an exit code
of 1). For example, if a package service is unable to be started, the control script will exit with an
error.
NOTE: This diagram is specific to legacy packages. Modular packages also run external scripts
and “pre-scripts” as explained above.
If the run script execution is not complete before the time specified in the run_script_timeout
parameter (page 171), the package manager will kill the script. During run script execution, messages
are written to a log file. For legacy packages, this is in the same directory as the run script and
has the same name as the run script and the extension.log. For modular packages, the pathname
is determined by the script_log_file parameter in the package configuration file (page 172)).
54 Understanding Serviceguard Software Components