|
The rcapd daemon enforces resource caps on collections of processes. Per-project physical memory caps are supported. For information about projects, see project(4).
When the resident set size (RSS) of a collection of processes exceeds its cap, rcapd takes action and reduces the RSS of the collection.
The virtual memory system divides physical memory into segments known as pages. To read data from a file into memory, the virtual memory system reads in individual pages. To reduce resource consumption, the daemon can page out, or relocate, infrequently used pages to an area outside of physical
memory.
In the project file, caps are defined for projects that have positive values for the following project attribute:
-
rcap.max-rss
- The total amount of physical memory, in bytes, that is available to the project's member processes
See project(4) for a description of project attributes.
You can configure rcapd through the use of rcapadm(1M). The daemon can be monitored with rcapstat(1). Configuration changes are incorporated into rcapd by sending it SIGHUP (see kill(1)), or according to the configuration interval (see rcapadm(1M)).
rcapd is an optional feature.
|
