User's Manual
Table Of Contents
- HP Process Resource Manager User Guide
- Contents
- Preface
- 1 Overview
- 2 Understanding how PRM manages resources
- 3 PRM configuration planning
- 4 Setting up PRM
- 5 Using PRM with HP System Management Homepage (SMH)
- 6 Using PRM with HP Systems Insight Manager (SIM)
- 7 Configuring and enabling PRM on the command line
- Quick start to using PRM’s command-line interface
- Configuring PRM
- The PRM configuration file
- Configuration tips and requirements
- Specifying PRM groups/controlling CPU resource use
- Controlling memory use
- Controlling applications
- Specifying PRM users
- Assigning secure compartments to PRM groups
- Assigning Unix groups to PRM groups
- Checking the configuration file
- Loading the PRM configuration
- Enabling resource managers
- Updating the configuration
- 8 Fine-tuning your PRM configuration
- 9 Administering PRM
- Moving processes between PRM groups
- Displaying application filename matches
- Displaying netgroup expansions
- Displaying accessible PRM groups
- Displaying state and configuration information
- Displaying application and configuration information
- Setting the memory manager’s polling interval
- Setting the application manager’s polling interval
- Disabling PRM
- Resetting PRM
- Monitoring PRM groups
- Logging PRM memory messages
- Logging PRM application messages
- Displaying groups’ allocated and used resources
- Displaying user information
- Displaying available memory to determine number of shares
- Displaying number of cores to determine number of shares
- Displaying past process information
- Displaying current process information
- Monitoring PRM with GlancePlus
- Monitoring PRM with OpenView Performance Agent (OVPA) / OpenView Performance Manager (OVPM)
- Automating PRM administration with scripts
- Protecting the PRM configuration from reboots
- Reconstructing a configuration file
- Special case of interest: Client/server connections
- Online cell operations
- Backing up PRM files
- A Command reference
- B HP-UX command/system call support
- C Monitoring PRM through SNMP
- D Creating Secure Resource Partitions
- E Using PRM with Serviceguard
- F Using PRM with HP Integrity Virtual Machines
- G PRM error messages
- Glossary
- Index
2. Remove the line corresponding to the application record you wish to remove. Application
records have the following form:
APPLICATION::::GROUP[,ALT_NAME[,...,ALT_NAME]]
NOTE: You may have multiple records for a single application. Be sure to locate all records
for an application in the configuration file and remove the appropriate records.
3. Save the file and exit the text editor.
4. Load the configuration using one of the following commands:
To initialize, moving user processes to the owners’ initial groups and moving applications to
their assigned groups, use the command:
#prmconfig -i [-fconfigfile] {-s | -c}
To keep the existing assignments of users, processes, and groups, use the command:
#prmconfig -k [-fconfigfile] {-s | -c}
Use the -f configfile option to specify a file other than the default /etc/prmconf. The -s
option displays warnings regarding the configuration file. (The -c option displays a subset
of the -s warnings.)
5. Enable PRM’s application manager if it is not already enabled:
#prmconfig -e APPL
Alternatively, enable all PRM resource managers using prmconfig -e without any additional
arguments:
#prmconfig -e
Launching an application under PRM
There are two ways to start an application under PRM:
• Start the application as you normally would.
The application manager automatically moves it to the PRM group assigned in the PRM
configuration file. A user must have the correct permissions to run the application.
• Use the prmrun command. For example, to start the critical_app application in its
assigned group CriticalApp:
# prmrun critical_app
The PRM configuration file must contain one record that has no alternate process names for
this application. If there is no such record, prmrun fails with an error.
The prmrun command allows any user to run an application in its assigned group as defined
in the PRM configuration file, assuming the user has execute permission on the application.
This means that any user can execute this command, even if they do not have permission to
use the application’s assigned PRM group.
The prmrun -g command can be used to override the PRM configuration file and run the
application in a specific PRM group if the user has access to the PRM group.
If the application manager is not running, and you do not use prmrun to start the application, it
runs in the current PRM group of the user who invokes it.
When the application manager is enabled, any applications not running in their assigned PRM
groups are moved to their assigned groups. The exception is an application moved to a specific
PRM group with prmmove -g or one started in a specific group with prmrun -g. If an application
does not have an assigned PRM group, it runs in the group of the invoking user.
Configuring PRM 69