Managing Serviceguard Eighteenth Edition, September 2010

will allow the failed package to halt after the successor_halt_timeout number of
seconds whether or not the dependent packages have completed their halt scripts.
2. Halts the failing package.
After the successor halt timer has expired or the dependent packages have all
halted, Serviceguard starts the halt script of the failing package, regardless of
whether the dependents' halts succeeded, failed, or timed out.
3. Halts packages the failing package depends on, starting with the package this
package immediately depends on. The packages are halted only if:
• these are failover packages, and
• the failing package can “drag” these packages to a node on which they can
all run.
Otherwise the failing package halts and the packages it depends on continue to
run
4. Starts the packages the failed package depends on (those halted in step 3, if any).
If the failed package has been able to drag the packages it depends on to the
adoptive node, Serviceguard starts them in the reverse of the order it halted them
in the previous step (that is, the package that does not depend on any other package
is started first).
5. Starts the failed package.
6. Starts the packages that depend on the failed package (those halted in step 1).
For More Information
For more information, see:
• The parameter descriptions for priority (page 293) and dependency_ (page 294), and
the corresponding comments in the package configuration template file
• The cmmakepkg (1m) manpage
• The white paper Serviceguard’s Package Dependency Feature, which you can find at
www.hp.com/go/hpux-serviceguard-docs
About Package Weights
Package weights and node capacities allow you to restrict the number of packages that
can run concurrently on a given node, or, alternatively, to limit the total package
“weight” (in terms of resource consumption) that a node can bear.
For example, suppose you have a two-node cluster consisting of a large system and a
smaller system. You want all your packages to be able to run on the large system at
the same time, but, if the large node fails, you want only the critical packages to run
on the smaller system. Package weights allow you to configure Serviceguard to enforce
this behavior.
Package Configuration Planning 187