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"?


Thanks!

CT
_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org

Reply via email to