Administering the Resource Capping Daemon With rcapadm

This section contains procedures for configuring the resource capping daemon with rcapadm. See rcapd Configuration and the rcapadm(1M) man page for more information. Using the rcapadm to specify a temporary resource cap for a zone is also covered.

If used without arguments, rcapadm displays the current status of the resource capping daemon if it has been configured.

How to Set the Memory Cap Enforcement Threshold

Caps can be configured so that they will not be enforced until the physical memory available to processes is low. See Memory Cap Enforcement Threshold for more information.

The minimum (and default) value is 0, which means that memory caps are always enforced. To set a different minimum, follow this procedure.

1. Become root or assume an equivalent role.
2. Use the -c option of rcapadm to set a different physical memory utilization value for memory cap enforcement.

   # rcapadm -c percent

   percent is in the range 0 to 100. Higher values are less restrictive. A higher value means capped project workloads can execute without having caps enforced until the system's memory utilization exceeds this threshold.

See Also

To display the current physical memory utilization and the cap enforcement threshold, see Reporting Memory Utilization and the Memory Cap Enforcement Threshold.

How to Set Operation Intervals

rcapd Operation Intervals contains information about the intervals for the periodic operations performed by rcapd. To set operation intervals using rcapadm, follow this procedure.

1. Become root or assume an equivalent role.
2. Use the -i option to set interval values.

   # rcapadm -i interval=value,...,interval=value 

   ---

   Note - All interval values are specified in seconds.

   ---

How to Enable Resource Capping

There are three ways to enable resource capping on your system. Enabling resource capping also sets the /etc/rcap.conf file with default values.

1. Become root or assume an equivalent role.
2. Enable the resource capping daemon in one of the following ways:

   • Turn on resource capping using the svcadm command.

     # svcadm enable rcap

   • Enable the resource capping daemon so that it will be started now and also be started each time the system is booted:

     # rcapadm -E

   • Enable the resource capping daemon at boot without starting it now by also specifying the -n option:

     # rcapadm -n -E

How to Disable Resource Capping

There are three ways to disable resource capping on your system.

1. Become root or assume an equivalent role.
2. Disable the resource capping daemon in one of the following ways:
   • Turn off resource capping using the svcadm command.

     # svcadm disable rcap

   • To disable the resource capping daemon so that it will be stopped now and not be started when the system is booted, type:

     # rcapadm -D

   • To disable the resource capping daemon without stopping it, also specify the -n option:

     # rcapadm -n -D

   ---

   Tip - Disabling the Resource Capping Daemon Safely

   ---

   Use rcapadm -D to safely disable rcapd. If the daemon is killed (see the kill(1) man page), processes might be left in a stopped state and need to be manually restarted. To resume a process running, use the prun command. See the prun(1) man page for more information.

How to Specify a Temporary Resource Cap for a Zone

This procedure is used to allocate the maximum amount of memory that can be consumed by a specified zone. This value lasts only until the next reboot. To set a persistent cap, use the zonecfg command.

1. Become root or assume an equivalent role.
2. Set a maximum memory value of 512 megabytes for the zone my-zone.

   # rcapadm -z testzone -m 512M