Managing HP Serviceguard for Linux Ninth Edition, April 2009

You can also use -e in combination with -m. This has the effect of starting all modules
up to and including the module identified by -m, except the module identified by -e.
In this case the excluded (-e) module must be earlier in the execution sequence (as
listed near the top of the package's configuration file) than the -m module. For example:
cmrunpkg -m sg/services -e sg/package_ip pkg1
NOTE: The full execution sequence for starting a package is:
1. The master control script itself
2. External pre-scripts
3. Volume groups
4. File systems
5. Package IPs
6. External scripts
7. Services
Characteristics of a Package Running in Partial-Startup Maintenance Mode
Serviceguard treats a package in maintenance mode differently from other packages
in important ways. The following points apply to a package running in maintenance
mode:
• Serviceguard ignores failures reported by package services, subnets, and file
systems; these will not cause the package to fail.
NOTE: But a failure in the package control script will cause the package to fail.
The package will also fail if an external script (or pre-script) cannot be executed
or does not exist.
• auto_run has no effect: the package will not be automatically failed over, halted,
or started.
• You cannot do online configuration as described under “Reconfiguring a Package”
(page 261).
• You cannot configure new dependencies involving this package; that is, you cannot
make it dependent on another package, or make another package depend on it.
See also “Dependency Rules for a Package in Partial-Startup Maintenance Mode”
(page 240).
• Once a package has started successfully in partial-startup maintenance mode, it
is “weightless”, meaning that its weight is not counted against node capacity; see
“About Package Weights” (page 128) for a discussion of weights and capacities.
This allows you to perform maintenance on any node in the cluster.
Maintaining a Package: Partial-Startup Maintenance Mode 239