Managing Serviceguard Eighteenth Edition, September 2010

7. Starts up any EMS (Event Monitoring Service) resources needed by the package
that were specially marked for deferred startup.
8. Exits with an exit code of zero (0).
Figure 3-14 Package Time Line (Legacy Package)
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, 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 (see (page 292)). Normal starts are recorded in the log, together
with error messages or warnings related to starting the package.
How Packages Run 83