IIRC for zones.cpu-shares the action is ignored. Something about "all infinite resources behave like this," i.e. CPU cycles aren't bounded. To the scheduler, you can always get more cycles if you're willint to wait a nanosecond or six.

Which makes sense to me - under what conditions would a process be signaled?

Christine Tran wrote:
The zones.cpu-shares rctl has a set of threshhold actions: none, deny and signal=. Say if I set the action as signal=TERM, who actually gets signaled? Is it the process in the zone that's currently queuing to get on CPU, or is it zoneadmd (which presumably will pass it back?)

I've always used (priv=priviledge,limit=n,action=none), that enforces the limit for me. What's the difference in behavior between "none" and "deny"?


Jeff VICTOR              Sun Microsystems            jeff.victor @ sun.com
OS Ambassador            Sr. Technical Specialist
Solaris 10 Zones FAQ:    http://www.opensolaris.org/os/community/zones/faq
zones-discuss mailing list

Reply via email to