Resource Controls Used in Non-Global Zones
For additional information about using a resource management feature in a zone, also
refer to the chapter that describes the feature in Part 1 of this
Any of the resource controls and attributes described in the resource management chapters
can be set in the global and non-global zone /etc/project file, NIS
map, or LDAP directory service. The settings for a given zone affect only
that zone. A project running autonomously in different zones can have controls set
individually in each zone. For example, Project A in the global zone can
be set project.cpu-shares=10 while Project A in a non-global zone can be set
project.cpu-shares=5. You could have several instances of rcapd running on the system, with each
instance operating only on its zone.
The resource controls and attributes used in a zone to control projects, tasks,
and processes within that zone are subject to the additional requirements regarding pools
and the zone-wide resource controls.
A “one zone, one pool” rule applies to non-global zones. Multiple non-global zones
can share the resources of one pool. Processes in the global zone, however,
can be bound by a sufficiently privileged process to any pool. The resource
controller poold only runs in the global zone, where there is more than
one pool for it to operate on. The poolstat utility run in
a non-global zone displays only information about the pool associated with the zone.
The pooladm command run without arguments in a non-global zone displays only information
about the pool associated with the zone.
Zone-wide resource controls do not take effect when they are set in the
project file. A zone-wide resource control is set through the zonecfg utility.