Managing HP Serviceguard for Linux, Seventh Edition, July 2007

Understanding Serviceguard Software Components
How Packages Run
Chapter 3 67
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 (see page 204). 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.
Normal and Abnormal Exits from the Halt Script
The package’s ability to move to other nodes is affected by the exit
conditions on leaving the halt script. The following are the possible exit
codes:
• 0—normal exit. The package halted normally, so all services are
down on this node.
• 1—abnormal exit, also known as no_restart exit. The package did
not halt normally. Services are killed, and the package is disabled
globally. It is not disabled on the current node, however.
• Timeout—Another type of exit occurs when the
halt_script_timeout is exceeded. In this scenario, the package is
killed and disabled globally. It is not disabled on the current node,
however.
Package Control Script Error and Exit Conditions
Table 3-4 shows the possible combinations of error condition, failfast
setting and package movement for failover packages.