[gridengine users] Linux Groups
rayson at scalablelogic.com
Fri Jun 8 18:19:46 UTC 2012
Thanks William - I was also wondering how others do this in the field.
As far as I know, only the primary group is considered - it was like
that since many, many years ago. But I was not sure how you guys
define ACLs that need to handle the non-primary group case.
IMO, using external tools to sync. Unix group membership to Grid
Engine internal ACL is a bit less nice, but that's what we can do for
And it may not be due to performance reasons - I have not looked into
this issue in detail but I believe it has to do with the Grid Engine
protocol. I was going to check if Grid Engine sends the non-primary
group IDs during job submission, but if Joseph is OK with using a cron
job to sync. membership then I can leave it aside for now - I will
need to work on a few more urgent things but will have more time later
On Fri, Jun 8, 2012 at 1:46 PM, William Hay <w.hay at ucl.ac.uk> wrote:
> On 8 June 2012 18:12, Joseph Farran <jfarran at uci.edu> wrote:
>> How does one set access to an OGE queue to have access from more than one Linux group?
>> So if I have Linux groups staff, bio, and chem, how do I make my "test" queue only accessible by these 3 groups?
> Create an access_list (with qconf -Au). Put @staff, at bio, at chem in the
> entries field. Add the access list to the user_lists entry
> of the queue. Alternatively create three separate lists for the three
> groups and add them all to the user_lists entry of the queue.
> NB: This only works for the user's primary group (some sort of
> performance thing I believe). If you want to have secondary groups
> then you could create a cron job to synchronise your Grid Engine
> access_list with your unix groups.
>> What kind of Q type do I setup?
>> users mailing list
>> users at gridengine.org
> users mailing list
> users at gridengine.org
More information about the users