On 06/03/09 16:02, Darren Reed wrote:
> I'm sponsoring this fast track for myself.
>
> PSARC admin
> ==========
> I tried to rename the case but:
> bin/sac_rename_title PSARC/2009/332 "New projects with boundless resources"
>
>
> ERROR: Could not find "PSARC/2009/332" in SAC Database files.
>
>
> ....maybe I'm driving the tools incorrectly? ...
>
> ...the case...
>
> This project seeks micro/patch binding.
>
> Problem
> =======
> The /etc/project file has been delivered (PSARC/1999/119) but its
> delivery did not define how we would add and name new projects,
> only that the numbers less than 100 were reserved. In addition,
> it did not offer full support of the features found in the project
> utilities such as prctl(1).
>
> Namespace
> =========
> Now that the file has been shipped for a number of years, we need
> to make reasonable guesses about what customers may have done since
> its delivery. One such guess is that they may have created projects
> with names similar or the same as SMF FMRIs or executables with which
> they are associated. Thus in creating a new project to be shipped by
> default, using a name such as "login" or "init" or "inetd" cannot be
> considered to be without risk.
>
> To provide us with the required flexibility for future enginering,
> this case proposes that all project names starting with "SUNW" be
> reserved and that they are not to be used by customers to define
> their own projects. This limitation needs to be documented in
> updates to project(4) and projadd(1M).
>
> Removing Limits
> ===============
> Using prctl(1), it is possible (depending on your privileges) to
> add, change or remove resource limits associated with projects.
> When using projadd(1M), it is only possible to define projects in
> terms of new limits they will have: it is not possible to remove
> an inherited resource limit using a project definition in
> /etc/project.
>
> Thus this case would like to propose that the /etc/project file
> be extended to allow resource limits to be removed. The suggested
> syntax is to simply be '<resource_name>=removed'. As an example,
> it would be possible to use "project.max-contracts=removed".
>
> Implementation
> ==============
> This cases proposes to implement the above suggestions and to
> deliver the following changes to the existing platform.
>
> New Project
> ~~~~~~~~~~~
> This case will deliver a new project called "SUNWinetd" that will
> be added to /etc/project. The line to be added is:
>
> SUNWinetd:5::::project.max-contracts=remove
- How will this cope with multiple occurrences of a resource control in
the project database? Taking the example from project(4)
beatles:100:The Beatles:john,paul,george,ringo::task.max-lwps=
(privileged,100,signal=SIGTERM),(privileged,110,deny);
process.max-file-descriptor
what would happen if one specified SUNWinetd:5::::task.max-lwps=remove ?
- You specifically mention /etc/project, so I assume a network based
project database isn't updated, right?
Menno
--
Menno Lageman - Sun Microsystems - http://blogs.sun.com/menno
