HP Process Resource Manager User's Guide
Configuring and enabling PRM on the command line
Configuring PRM
Chapter 7154
When the prmconfig -i, prmconfig -k, or GUI equivalents complete
without finding errors, an internal copy of the configuration file is made.
This copy is used by the PRM commands as well as the PRM-aware
HP-UX commands while PRM is configured. (For information on these
PRM-aware commands, see “HP-UX command/system call support” on
page 231.) Thus, the original configuration file can be edited without
disrupting PRM. However, to be safe, you should create a work copy to
make modifications to the configuration file.
If a PRM configuration is not already loaded, using either prmconfig -i
or prmconfig -k (or the GUI equivalents) moves all currently running
processes, not owned by any root user, to their owners’ initial groups.
However, if a user’s initial group is not defined in the configuration file or
there is no record for the user, the processes are placed in OTHERS
(PRMID 1), the user default group. This occurs even if the PRM
scheduler has not been enabled. Any configured application is moved to
the group assigned in the PRM configuration file.
If a PRM configuration is already loaded and some processes have been
moved to alternate groups, the two types of configuration loads have
different results, as shown in Table 7-1.
Table 7-1 Differences in loads when a configuration is already loaded
Command Description
prmconfig -i
(Initialize or Move)
Loads a PRM configuration as follows:
• Places processes subject to compartment, application, user, or
Unix group records in their assigned PRM groups.
• Places all currently running processes—not owned by root—in
their owners’ initial groups, as defined in the owners’ user
records. The initial group is OTHERS for nonroot users without
user records.
If root has a user record, root logins that occur after the load are
placed in the PRM group specified as the initial group in the user
record. However, any root processes that exist when the load
happens are left as is, unless the process is executing in a group
that is deleted in the new configuration, in which case, the
processes are moved to the specified initial group.