HP-UX Processor Sets

HP-UX Processor Sets 11
ÿ Superuser can perform any processor set operation.
ÿ A new privilege group, PRIV_PSET, is defined for processor set operations.
(Note:
Please refer to the setprivgrp(2) manpage for more information on privilege groups
in HP-UX.)
Users with PRIV_PSET privilege can perform any processor set
operation. This allows someone to acquire “restricted” superuser permissions for
processor set management.
ÿ Every processor set is assigned a user-owner, who may or may not have superuser
or PRIV_PSET privileges. The processor set creator becomes the default owner.
Ownership is an attribute of a processor set; it may be changed to any other user with
appropriate permissions. Ownership is identified by the user id (UID) of the owner.
ÿ Every processor set is assigned a user group and is identified by the group id (GID)
of the owner.
ÿ All operations (except the topology query operations) on a processor set require
some type of access permission.
ÿ Ownership is used to define an access permissions model similar to the UNIX file
system access permissions. Any user is in one of the Owner, Group, or Others
categories, each with READ, WRITE and EXEC permissions for the user. Access
permissions are an attribute of a processor set; they may be changed to grant or
reject permission to a user for an operation on a processor set.
Table 1: Ownership and Access Permissions Model for Processor Sets
Pset Operation Superuser PRIV_PSET
User
Users with Pset READ, WRITE,
EXEC Access Permissions
Any
Other
User
Create a Pset Yes Yes N/A (Pset is not created as yet) Yes
Destroy a Pset Yes Yes Yes with WRITE permission No
Source
Pset
Target
Pset
Permissions
Default
Pset
Non
Default
Pset
N/A (Non-root
and non-
PRIV_PSET
users cannot
have WRITE
permission to
Default Pset)
Reassign a
processor to
another Pset
Yes Yes
Non
Default
Pset
Non
Default
Pset
Yes with WRITE
permissions in
both Psets
No