HP-UX HB v13.00 Ch-19 - PRM

HP-UX Handbook – Rev 13.00 Page 12 (of 31)
Chapter 19 Process Resource Manager (PRM)
October 29, 2013
/u01/app/oracle/product/10.2.0/db_1/bin/tnslsnr::::Mktg, ’tnslsnr.*Mktg’
/u01/app/oracle/product/10.2.0/db_1/bin/tnslsnr::::Support, ’tnslsnr.*Support’
Launching a script under PRM
To always run a script in a specific PRM group, use an application record. In this record, specify
the full path of the shell or interpreter used in the script as the application. Also, give the name -
without the path - of the script as an alternate name.
For example, consider a script named foo.sh that uses sh to execute its contents. In this scenario,
an application record might look like this:
/sbin/sh::::GroupA,foo.sh
NOTE: The full path of the shell/interpreter used in the script must appear in either the file
/etc/shells or the file /opt/prm/shells.
Because the full pathname is not required for the script, a rogue user can get access to PRM
groups - that otherwise would not be accessible - by using the name of the script for new script
wrappers.
In the Oracle example above the groups ORA_ORM and ORA_BFL were created.
Additionally the following two groups exist but do not have to be specified:
PRM_SYS
PRM automatically assigns system processes to the group PRM_SYS (PRMID 0) and calculates
this group’s resource needs. You do not need to specify the PRM_SYS group in the PRM
configuration file.
Non root users cannot have access to the system group PRM_SYS (PRMID 0).
OTHERS
The user default group, OTHERS (PRMID 1), is required in the PRM configuration file.
Resource Entitlement per PRM Group
The command prmavail(1) displays a quick information about the available system resources:
# prmavail
16 CPUs
8388608 real memory pages or 32768 MB available (PRM estimate)
5 volume groups
/dev/vg00
/dev/vgora
/dev/vgdbt
Now you need to decide how to divide the resources (CPU, MEMORY, DISK) among the PRM