How should you permanently restrict the non-global zone…

How should you permanently restrict the non-global zone testzone so that it does not use more than 20 CPU
shares while it is running?

A.
While configuring the zone, add this entry:add rct1set name = capped.cpu-sharesadd value (priv =
privileged, limit = 20, action = none)endexit

B.
While configuring the zone, add this entry: add rct1set name= zone.cpu-sharesadd value (priv=privileged,
limit=20, action=none)endexitfrom command line, enter: # dispadmin – d FSS

C.
From the command line enter: #prct1 -n zone.cpu-shares – r – v 20 – i zone testzone

D.
From the command line, enter:#prct1 – n zone.cpu-shares – v 80 – r – i zone global

Explanation:
The prctl utility allows the examination and modification of the resource controls associated with an active
process, task, or project on the system. It allows access to the basic and privileged limits and the current usage
on the specified entity.
How to Change the zone.cpu-shares Value in a Zone Dynamically
This procedure can be used in the global zone or in a non-global zone.
For more information about roles, see Configuring and Using RBAC (Task Map) in System Administration
Guide: Security Services.
# prctl -n zone.cpu-shares -r -v value -i zone zonename
idtype is either the zonename or the zoneid. value is the new value.
Note: project.cpu-shares
Number of CPU shares granted to a project for use with the fair share scheduler