PSARC/2009/332 New projects with boundless resources

[Menno Lageman]

On 06/03/09 16:48, Darren Reed wrote:
> 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.

Sorry, I was too quick with copy/paste: the 'SUNWinetd' should have been 
'beatles' of course. Let's try again:

- 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 beatles:100::::task.max-lwps=remove ? 
Would this remove the 'privileged,100,signal=SIGTERM' occurance, the 
'privileged,110,deny' occurrence, both occurrences, or none from 
/etc/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.

I don't think the regular instalation process updates an external 
project database in NIS or LDAP.

Menno
-- 
Menno Lageman - Sun Microsystems - http://blogs.sun.com/menno