Managing HP Serviceguard A.12.00.00 for Linux, June 2014

6.1.4.58 user_name
Specifies the name of a user who has permission to administer this package. See also user_host
(page 200) and user_role; these three parameters together define the access control policy for
this package (see “Controlling Access to the Cluster” (page 169)). 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 171) for further discussion and examples.
6.1.4.59 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 169) for more information.
6.2 Generating the Package Configuration File
When you have chosen the configuration modules your package needs (see “Choosing Package
Modules” (page 179)), you are ready to generate a package configuration file that contains those
modules. This file will consist of a base module (failover, multi-node or system multi-node) plus the
modules that contain the additional parameters you have decided to include.
6.2.1 Before You Start
Before you start building a package, create a subdirectory for it in the $SGCONF directory, for
example:
mkdir $SGCONF/pkg1
(See “Understanding the Location of Serviceguard Files” (page 143) for information about
Serviceguard pathnames.)
6.2.2 cmmakepkg Examples
The cmmakepkg command generates a package configuration file. Some examples follow; see
the cmmakepkg (1m) manpage for complete information. All the examples create an editable
configuration file pkg1.conf in the $SGCONF/pkg1 directory.
NOTE: If you do not include a base module (or default or all) on the cmmakepkg command
line, cmmakepkg will ignore the modules you specify and generate a default configuration file
containing all the parameters.
For a complex package, or if you are not yet sure which parameters you will need to set, the
default may be the best choice; see the first example below.
You can use the-v option with cmmakepkg to control how much information is displayed online
or included in the configuration file. Valid values are 0, 1 and 2. -v 0 removes all comments; -v
1 includes a brief heading for each parameter; -v 2 provides a full description of each parameter.
The default is level 2.
6.2 Generating the Package Configuration File 201