On Tue, Oct 31, 2006 at 03:28:31PM -0800, Dan Price wrote:
> On Tue 31 Oct 2006 at 03:24PM, Steve Lawrence wrote:
> > It seems reasonable to amend this case to say:
> > 1.
> > Any process with priv_sys_resource running in the global zone's
> > system project (project 0) will not subject to project.* or zone.*
> > resource controls. System daemons which wish to be subject to the
> > global zone's resource controls can drop priv_sys_resource.
> This "feels" risky for a patch... the effect here is to "un-manage"
> things which the customer may be expecting to be resource managed,
> potentially including a workload. Or is the point that no-one using
> RM will be relying on the system project to limit things?
Currently, if rctls are specified in project(4) for the system project, they
are never actually applied during boot. While this could be considered a bug,
this also means that currently, by default, admins will have to take additional
manual steps to resource manage project 0. They are more likely to put what
they want to manage in a new/different project, and use project(4) to configure
> This implies that can't give the system project 10 (or 100) shares
> after this proposal?
> Daniel Price - Solaris Kernel Engineering - [EMAIL PROTECTED] -
zones-discuss mailing list