Menno Lageman wrote:
> 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?
This case proposes no changes to the behaviour of the system if
there are multiple projects defined with the same name.
For example, the same question might be asked of this scenario:
beatles:100:The Beatles:john,paul,george,ringo::task.max-lwps=
(privileged,100,signal=SIGTERM),(privileged,110,deny);
process.max-file-descriptor
beatles:100::::task.max-lwps=(privileged,1,signal=SIGINT)
Given that the man page project(4) does not describe what happens
when there are multiple lines present with the same project name,
nor if it should or should not be done, the behaviour will remain as
it is: undefined.
Darren
