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?

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?

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.
From the command line, enter: #prct1 – n zone.cpu-shares – v 80 – r – i zone global

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

C.
While configuring the zone, add this entry: add rct1 set name= zone.cpu-shares add
value (priv=privileged, limit=20, action=none) end exit from command line, enter: #
dispadmin – d FSS

D.
While configuring the zone, add this entry: add rct1 set name = capped.cpu-shares add
value (priv = privileged, limit = 20, action = none) end exit

Explanation:



Leave a Reply 1

Your email address will not be published. Required fields are marked *

19 − 10 =