Managing Serviceguard A.11.20, March 2013

script is executed with the stop parameter. This script carries out the following steps (also shown
in Figure 24):
1. Halts any deferred resources that had been started earlier.
2. Halts all package services.
3. Executes any customer-defined halt commands (legacy packages only) or external_scripts
(modular packages only (page 256)).
4. Removes package IP addresses from the NIC on the node.
5. Unmounts file systems.
6. Deactivates volume groups.
7. Exits with an exit code of zero (0).
8. Executes any external_pre_scripts (modular packages only (page 256)).
Figure 24 Legacy Package Time Line for Halt Script Execution
At any step along the way, an error will result in the script exiting abnormally (with an exit code
of 1). Also, if the halt script execution is not complete before the time specified in the
HALT_SCRIPT_TIMEOUT, the package manager will kill the script. During halt 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 241). Normal starts are recorded in the log, together with error messages or warnings
related to halting the package.
NOTE: This diagram applies specifically to legacy packages. Differences for modular scripts are
called out above.
66 Understanding Serviceguard Software Components