PSARC/2009/332 New projects with boundless resources

[Darren Reed]

Menno Lageman wrote:
...
>>
>> 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 ?

Any object in Solaris can only belong to one project.
So a process either belongs to the "beatles" project or it belongs to 
the "SUNWinetd" project.

> - You specifically mention /etc/project, so I assume a network based 
> project database isn't updated, right?

That would be (re)built as part of the installation process.
It is a similar problem to updating /etc/services, etc.

Darren