Managing HP Serviceguard for Linux, Seventh Edition, July 2007

Building an HA Cluster Configuration
Preparing Your Systems
Chapter 5 145
server_args = -f /user/local/cmom/log/cmomd.log -r
/user/local/cmom/run
to
server_args = -i -f /user/local/cmom/log/cmomd.log -r
/user/local/cmom/run
3. Restart xinetd: /etc/init.d/xinetd restart
Access Roles
Serviceguard access control policies define what a user on a remote node
can do on the local node. These are known as Access Roles or Role
Based Access (RBA). This manual uses Access Roles. Serviceguard
recognizes two levels of access, root and non-root:
• Root Access: Users authorized for root access have total control over
the configuration of the cluster and packages. These users have full
operating-system-level root privileges for the node, the same
privileges as the local root user.
• Non-root Access: Non-root users can be assigned one of four roles:
— Monitor: These users have read-only access to the cluster and its
packages. They can use the cmviewcl, cmquerycl, cmgetconf,
and cmviewconf commands (and perform equivalent functions in
Serviceguard Manager).
— (single-package) Package Admin: Applies only to a specific
package. (This is the only access role defined in the package
configuration file; the others are defined in the cluster
configuration file.) These users can use the commands cmrunpkg,
cmhaltpkg, and cmmodpkg for the specified package (and perform
the equivalent functions in Serviceguard Manager) but cannot
configure or create packages. Package Admin also includes the
cluster-wide privileges of the Monitor role.
— (all-packages) Package Admin: Applies to all packages in the
cluster and so is defined in the cluster configuration file. These
users can use the commands cmrunpkg, cmhaltpkg, and
cmmodpkg for all packages (and perform the equivalent functions
in Serviceguard Manager) but cannot configure or create
packages. Package Admin includes the cluster-wide privileges of
the Monitor role.