[torqueusers] Problems with acl_group_enable and acl_group_sloppy
Bas van der Vlies
basv at sara.nl
Tue Oct 3 00:43:44 MDT 2006
>>
>> Must we not skip this flag when we use the acl_group_sloppy setting?
>> Because the primary group does not decide if the job should run and -
>> W flag can be used for accounting purposes and the job is still
>> allowed to run because the acl_group_sloppy setting.
>
> The original idea was that if the user was supplying groups, then listen
> to the user. Imagine a scenerio where a routing queues were setup for
> different projects (group acls) and a user was part of multiple
> projects. By disabling sloppy with group_list, the user has control
> over the routing of the job.
>
Oke, that is also an valid reason ;-) The check for the user supplied
group_list is later then this check i assume?
regards
--
********************************************************************
* *
* Bas van der Vlies e-mail: basv at sara.nl *
* SARA - Academic Computing Services phone: +31 20 592 8012 *
* Kruislaan 415 fax: +31 20 6683167 *
* 1098 SJ Amsterdam *
* *
********************************************************************
More information about the torqueusers
mailing list