| Skip Navigation Links | |
| Exit Print View | |
|
Resource Management, Oracle Solaris Zones, and Oracle Solaris 10 Zones Developer's Guide Oracle Solaris 11.1 Information Library |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Resource Management, Oracle Solaris Zones, and Oracle Solaris 10 Zones Developer's Guide Oracle Solaris 11.1 Information Library |
1. Resource Management in the Oracle Solaris Operating System
3. Using the C Interface to Extended Accounting
4. Using the Perl Interface to Extended Accounting
Resource Controls Flags and Actions
Resource Control Values and Privilege Levels
Global Actions and Global Flags
Resource Control Sets Associated With a Zone, Project, Processes, and Tasks
Resource Controls Associated With a Project
Resource Controls Associated With Tasks
Resource Controls Associated With Processes
Signals Used With Resource Controls
Resource Controls API Functions
Operate on Action-Value Pairs of a Resource Control
Operate on Local Modifiable Values
Retrieve Local Read-Only Values
Retrieve Global Read-Only Actions
Resource Control Code Examples
Master Observing Process for Resource Controls
List all the Value-Action Pairs for a Specific Resource Control
Set project.cpu-shares and Add a New Value
Set LWP Limit Using Resource Control Blocks
zonestat Utility for Monitoring Zones Resource Usage
7. Design Considerations for Resource Management Applications in Oracle Solaris Zones
Consider the following issues when writing your application:
The resource control block is opaque. The control block needs to be dynamically allocated.
If a basic resource control is established on a task or project, the process that establishes this resource control becomes an observer. The action for this resource control block is applied to the observer. However, some resources cannot be observed in this manner.
If a privileged resource control is set on a task or project, no observer process exists. However, any process that violates the limit becomes the subject of the resource control action.
Only one action is permitted for each type: global and local.
Only one basic rctl is allowed per process per resource control.
|