prmconfig(1)prmconfig(1)NAMEprmconfig - configure the Process Resource Manager (PRM)
SYNOPSIS
configfile] [manager]]
interval manager] manager [logarg]] mode]
DESCRIPTION
configures, enables, disables, and resets PRM. Configuration, state,
and mode information are displayed whenever PRM has been configured by
This information consists of PRM group names, PRMIDs, and resource
shares/caps for each PRM group, as well as resource manager polling
interval lengths. State information consists of an enabled/disabled
indication for each PRM manager configured (CPU, memory, disk, and
application) and for the modes and
You can also use with the option to validate the configuration file.
Real-time processes are not restricted by the PRM configuration, but
are charged against group usage.
To configure PRM and enable PRM resource and application managers at
system boot time, set control variables in These variables are
explained in the file itself.
COMMAND AVAILABILITY
Only the superuser can configure or reset PRM. Also, only the supe‐
ruser can enable or disable PRM managers.
Any user can print current configuration, state, and mode information
using with no options; and, any user can validate a configuration file
using
OPTIONS
Running prints current configuration, state, and mode information when
or no options are specified.
Display version information and exit.
Configure (or reconfigure)
PRM using the default configuration file (/etc/prmconf) or the
file specified by configfile. (For information on configuration
files, see prmconf(4).)
This option does not alter the current state of any resource until
a PRM resource manager is enabled for that resource. In other
words, if the HP-UX scheduler is in effect, it remains in effect.
Similarly, if PRM is already managing resources, it continues to
do so. Use to enable PRM resource management.
The option creates the PRM groups specified in the configuration
file and then moves all currently running configured compartment,
application, and user processes to their assigned PRM groups.
If an application is not assigned to a group or is assigned to a
group that does not exist in the new configuration, it is moved to
the initial group of the user running the application. If the
user's initial group is not defined in the configuration file or
there is no user record for the owner, the process is placed in
PRMID 1, the user default group.
Configure (or reconfigure)
PRM as in the option, but keep processes in the PRM groups they
are currently running in, with a few exceptions.
The exceptions are:
User processes running in PRMID 0 (the PRM system group) and pro‐
cesses running in groups that do not exist in the new configura‐
tion
Each process is moved to the initial group of its user ID, as
defined in the configuration file. If there is no record for
a user, the process is placed in PRMID 1, the user default
group.
User processes where the initial group is a PSET PRM group--and at
least one PSET group in the configuration has specific cores
assigned to it (A core is the actual data-processing engine within
a processor. A core might support multiple execution threads, as
explained in the section HYPER-THREADING in the prm(1) manpage.)
Each process is moved to the initial group of its user as
defined in the configuration file.
Application processes matching application records running in
PRMID 0 or in a PSET PRM group--and at least one PSET group in the
configuration has specific cores assigned to it
These processes are moved to the assigned groups when the
application manager is enabled.
Note that options -i and -k are equivalent when PRM is unconfig‐
ured.
Perform supplemental validation checks on the configuration file.
Supplemental checks include:
+ Duplicate group names
+ Duplicate user names
+ Undefined groups in user access lists
+ Mismatches between user names in the configuration file and
logins in the password files accessible by the C function such
as /etc/passwd.
Perform a subset of the
checks on the configuration file. The checks include:
+ Duplicate group names
+ Duplicate user names
+ Undefined groups in user access lists
+ Verify each user name in the configuration is in the password
file
The difference between the and checks are in the last check. The
check verifies every user name in the configuration is in the
password file and that every user name in the password file is in
the configuration. The check only verifies that user names in the
configuration are in the password file.
configfile
Use the configuration file given by configfile for the or options.
When configfile is not specified, PRM uses the default PRM config‐
uration file which is described in prmconf(4).
[manager]
Disable PRM resource and application managers.
The current configuration is not changed.
If you do not specify a manager argument, all currently enabled
PRM managers are disabled. If a manager argument is provided,
only the specified manager is disabled. When specifying multiple
manager arguments, precede each argument with
Specify one of the following keywords to disable the respective
manager:
PRM CPU scheduling feature
PRM memory manager
PRM application manager
PRM disk bandwidth management feature
When you use any mode settings associated with the resource man‐
ager that is disabled are set to the defaults. For example, dis‐
abling the PRM CPU scheduler automatically causes the associated
CPU cap mode to be disabled.
[manager]
Enable PRM resource and application managers.
The current configuration is not changed.
If you do not specify a manager argument, all currently configured
PRM managers are enabled. If a manager argument is provided, then
only the specified manager is enabled. When specifying multiple
manager arguments, precede each argument with
Specify one of the following keywords to enable the respective
manager:
PRM CPU scheduling feature
PRM memory manager
PRM application manager
PRM disk bandwidth management feature
You must enable a resource manager prior to setting any associated
mode to a nondefault state. For example, you can enable the CPU
cap mode only after the PRM CPU scheduler is enabled.
You must enable the application manager for PRM to place applica‐
tion processes, user processes, compartment processes, and Unix
group processes in their assigned groups.
Reset
PRM to its boot-time state.
When PRM is reset:
All PRM managers that are currently running are disabled and
shutdown.
All PRM groups are removed from the system and replaced with
a single group (PRMID 0).
All processes on the system are re-assigned to this single
group.
PRM is then considered "unconfigured".
Unlock a PRM configuration lock.
This lock is put in place to prevent multiple parties from chang‐
ing the PRM configuration simultaneously. Various HP-UX manage‐
ment products can all lock the configuration file. If one of these
products terminates without releasing the lock, use the option to
force the lock to be released.
Include parent hierarchical groups in output. For information on
hierarchical groups, see prmconf(4).
Print the PRM group names in wide-column format, exceeding the
30-column default if necessary to avoid clipping any names.
Include number of cores and core IDs for PSET PRM groups in output.
For more information on PSET PRM groups, see prmconf(4).
Show whether memory isolation is being used.
interval manager
Override the polling interval (time between pollings) for the
specified resource manager.
Both the interval argument and the manager argument are required
with this option.
interval
Indicates the length of the PRM manager's polling interval in
seconds.
manager
Specifies the PRM manager.
Use one of the following keywords to specify a manager:
PRM memory manager (default interval is 10 seconds; min‐
imum is one second)
PRM application manager (default interval is 30 seconds;
minimum is one second)
manager [logarg]
Log informational messages to the system log file (/var/adm/sys‐
log/syslog.log) using the syslog daemon for the specified resource
manager (see syslogd(1M)).
The required manager argument specifies the PRM manager that is to
log.
Valid manager keywords are:
The PRM memory manager--logs memory usage statistics per
group.
The application manager--logs information about processes
moved at each interval.
An optional logarg argument causes logging for the specified PRM
manager to stop.
mode
Specify a PRM operation mode. To specify multiple modes with the
same command, repeat mode.
is required and can be:
Enables PRM CPU resource capping for all FSS PRM groups in
the configuration--based on their shares values. (For infor‐
mation on capping CPU consumption on a per-group basis, see
the prmconf(4) manpage.)
When mode is enabled, CPU usage for each FSS PRM group is
capped at the group's shares value (see WARNINGS).
(Default) Disables PRM CPU resource capping based on each
group's shares value. (Per-group capping is still enforced.)
Places processes in PRM groups based on real user IDs. You
can set this mode only in the reset state. Use to reset.
(Default) Places processes in PRM groups based on effective
user IDs.
RETURN VALUE
returns exit status if no errors occur, and otherwise.
EXAMPLES
Print the current configuration:
Configure PRM and enable PRM resource managers, moving processes to
their assigned PRM groups:
Configure PRM, keeping processes in their current PRM groups:
Disable the memory manager, without disturbing other resource managers
or changing the configuration:
Reset PRM to its boot-time state:
Validate the default configuration file (/etc/prmconf) including sup‐
plemental checks, without changing the state, configuration, or mode:
Configure PRM after validating the configuration file and performing
supplemental checks:
Validate the specified configuration file including supplemental
checks, without changing the state, configuration, or mode:
configfile
Configure PRM and enable the PRM CPU scheduler using the specified con‐
figuration file:
configfile
Set the application manager polling interval to 15 seconds. Processes
are checked every 15 seconds to make sure the configured application
processes, launched manually without using prmrun or created as child
processes, get moved to their assigned PRM groups:
Tell the application manager to start logging processes moved during
polling intervals using the syslog daemon.
Enable the PRM CPU scheduler and cap CPU usage at each group's shares
value.
WARNINGS
The method used in and to move application processes to their assigned
groups cannot guarantee that all are moved. For example, some system
and script processes with full paths longer than characters and file‐
names longer than characters cannot be moved. Also, if applications
have alternate names longer than characters, these application pro‐
cesses may not get moved. If this happens, use to move them to their
appropriate groups.
Application logging may cause the log file to grow rapidly, depending
on the number of processes being launched in each interval and the
interval frequency.
The PRM Group field in the configuration display is truncated to char‐
acters unless you specify the option.
Enabling PRM CPU capping may result in reduced system throughput
because a PRM group's unused CPU resource is not available for use by
processes in other groups.
Online cell operations
If you want to perform online cell operations, and:
· Your PRM configuration contains memory records
Stop memory management then after the online cell operation has com‐
pleted, restart memory management
· Your PRM configuration uses PSETs
Reset PRM then after the online cell operation has completed, restart
PRM management
For more information on online cell operations, see parolrad(1M).
AUTHOR
was developed by HP.
FILES
default PRM configuration file
system log file used by PRM
startup file used by /sbin/init.d/prm
start/stop script useful for testing /etc/rc.config.d/prm options
and fully stopping PRM without manually
killing processes
SEE ALSOat(1), id(1), login(1), prm(1), prm1d(1), prmagt(1), prmanalyze(1),
prmavail(1), prmlist(1), prmloadconf(1), prmmonitor(1), prmmove(1),
prmrecover(1), prmrun(1), ps(1), cron(1M), exec(2), fork(2), prm‐
conf(4).
HP Process Resource Manager User's Guide (/opt/prm/doc/PRM.ug.pdf)
HP Process Resource Manager homepage (http://www.hp.com/go/prm)
prmconfig(1)
