Managing Serviceguard A.11.20, March 2013

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 197)). 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 199) 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 197) for more information.
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 “Configuring a Legacy Package” (page 307) for more information.
PATH Specifies the path to be used by the script.
SUBNET Specifies the IP subnets that are to be monitored for the
package.
RUN_SCRIPT and HALT_SCRIPT Use the full pathname of each script.
These two parameters allow you to separate package run
instructions and package halt instructions for legacy
packages into separate scripts if you need to. In this case,
make sure you include identical configuration information
(such as node names, IP addresses, etc.) in both scripts.
In most cases, though, HP recommends that you use the
same script for both run and halt instructions. (When the
package starts, the script is passed the parameter start;
when it halts, it is passed the parameter stop.)
DEFERRED_RESOURCE_NAME Add DEFERRED_RESOURCE_NAME to a legacy package
control script for any resource that has a RESOURCE_START
setting of DEFERRED.
Choosing Package Modules 257