Managing HP Serviceguard A.11.20.10 for Linux, December 2012

If more than one external_pre_script is specified, the scripts will be executed on package
startup in the order they are entered into the package configuration file, and in the reverse order
during package shutdown.
See “About External Scripts” (page 122), as well as the comments in the configuration file, for more
information and examples.
6.1.4.51 external_script
The full pathname of an external script. This script is often the means of launching and halting the
application that constitutes the main function of the package. New for modular packages.
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 122), as well as the comments in the configuration file, for more
information and examples. See also service_cmd (page 177).
6.1.4.52 user_host
The system from which a user specified by user_name (page 184) 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 the hostname portion, of the fully qualified domain name). As with user_name, be careful
to spell the keywords exactly as given.
6.1.4.53 user_name
Specifies the name of a user who has permission to administer this package. See also user_host
(page 184) and user_role; these three parameters together define the access control policy for
this package (see “Controlling Access to the Cluster” (page 152)). 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 154) for further discussion and examples.
6.1.4.54 user_role
Must be package_admin, allowing the user access to the cmrunpkg, cmhaltpkg, and cmmodpkg
commands (and the equivalent functions in Serviceguard Manager) and to the monitor role for
the cluster. See “Controlling Access to the Cluster” (page 152) for more information.
6.1.4.55 Additional Parameters Used Only by Legacy Packages
IMPORTANT: The following parameters are used only by legacy packages. Do not try to use
them in modular packages. See “Creating the Legacy Package Configuration ” (page 225) for more
information.
184 Configuring Packages and Their Services