Managing Serviceguard Eighteenth Edition, September 2010

The script is executed on package startup after volume groups and file systems are
activated and IP addresses are assigned, but before services are started; and during
package shutdown after services are halted but before IP addresses are removed and
volume groups and file systems deactivated.
If more than one external_script is specified, the scripts will be executed on package
startup in the order they are entered into this file, and in the reverse order during
package shutdown.
See “About External Scripts” (page 197), and the comments in the configuration file,
for more information and examples.
user_name
Specifies the name of a user who has permission to administer this package. See also
user_host and user_role; these three parameters together define the access-control policy
for this package (see “Controlling Access to the Cluster” (page 251)). These parameters
must be defined in this order: user_name, user_host, user_role.
Legal values for user_name are any_user or a maximum of eight login names from
/etc/passwd on user_host.
NOTE: Be careful to spell any_user exactly as given; otherwise Serviceguard will
interpret it as a user name.
Note that the only user_role that can be granted in the package configuration file is
package_admin for this particular package; you grant other roles in the cluster
configuration file. See “Setting up Access-Control Policies” (page 254) for further
discussion and examples.
user_host
The system from which a user specified by user_name can execute
package-administration commands.
Legal values are any_serviceguard_node, or cluster_member_node, or a specific
cluster node. If you specify a specific node it must be the official hostname (the
hostname portion, and only thehostname portion, of the fully qualified domain name).
As with user_name, be careful to spell the keywords exactly as given.
user_role
Must be package_admin, allowing the user access to the cmrunpkg, cmhaltpkg,
and cmmodpkg commands (and the equivalent functions in Serviceguard Manager)
for this package, and to the Monitor role for the cluster. See “Controlling Access to the
Cluster” (page 251) for more information.
310 Configuring Packages and Their Services