1rcapd(1M) System Administration Commands rcapd(1M)
2
6 rcapd - resource cap enforcement daemon
7
9 rcapd [-d]
10
13 The rcapd daemon enforces resource caps on collections of processes.
14 Per-project and per-zone physical memory caps are supported. For infor‐
15 mation about projects, see project(4). For zones information, see
16 zones(5)
17 When the resident set size (RSS) of a collection of processes exceeds
20 its cap, rcapd takes action and reduces the RSS of the collection.
21 The virtual memory system divides physical memory into segments known
24 as pages. To read data from a file into memory, the virtual memory sys‐
25 tem reads in individual pages. To reduce resource consumption, the dae‐
26 mon can page out, or relocate, infrequently used pages to an area out‐
27 side of physical memory.
28 In the project file, caps are defined for projects that have positive
31 values for the following project attribute:
32 rcap.max-rss The total amount of physical memory, in bytes, that is
34 available to the project's member processes
35 See project(4) for a description of project attributes.
39 For a system with one or more zones, you can dynamically set the
42 rcap.max-rss value for a zone with rcapadm(1M). To set a persistent cap
43 on memory usage within a zone, you use zonecfg(1M).
44 You configure rcapd through the use of rcapadm(1M). The daemon can be
47 monitored with rcapstat(1). Configuration changes are incorporated into
48 rcapd by sending it SIGHUP (see kill(1)), or according to the configu‐
49 ration interval (see rcapadm(1M)).
50
52 The following option is supported:
53 -d Enable debug mode. Messages are displayed on the invoking user's
55 terminal.
56
59 Example 1 Setting Resident Set Size Cap Attribute
60 The following line in the /etc/project database sets an RSS cap of
63 1073741824 bytes for a project named foo.
64 foo:100::foo,root::rcap.max-rss=10737418240
67
70 The following exit values are returned:
71 0 Successful completion.
73 1 An error occurred.
76 2 Invalid command-line options were specified.
79
82 /etc/project Project database.
83
86 See attributes(5) for descriptions of the following attributes:
87 ┌─────────────────────────────┬─────────────────────────────┐
92 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
93 ├─────────────────────────────┼─────────────────────────────┤
94 │Availability │SUNWrcapu │
95 ├─────────────────────────────┼─────────────────────────────┤
96 │Interface Stability │Evolving │
97 └─────────────────────────────┴─────────────────────────────┘
98
100 rcapstat(1), svcs(1), rcapadm(1M), zonecfg(1M), svcadm(1M), project(4),
101 attributes(5), smf(5), zones(5)
102 "Physical Memory Control Using the Resource Capping Daemon" in System
105 Administration Guide: Solaris Containers-Resource Management, and
106 Solaris Zones
107
109 If killed with SIGKILL, rcapd can leave processes in a stopped state.
110 Use SIGTERM to cause rcapd to terminate properly.
111 A collection's RSS can exceed its cap for some time before the cap is
114 enforced, even if sufficient pageable memory is available. This period
115 of time can be reduced by shortening the RSS sampling interval with
116 rcapadm.
117 The rcapd service is managed by the service management facility,
120 smf(5), under the service identifier:
121 svc:/system/rcap:default
123 Administrative actions on this service, such as enabling, disabling, or
128 requesting restart, can be performed using svcadm(1M). The service's
129 status can be queried using the svcs(1) command.
130SunOS 5.11 19 Dec 2006 rcapd(1M)