Reuti <[email protected]> writes:
>> Specifically, with a rule like this:
>>
>> limit users {!@longusers} to h_rt=432000
>
> Can you try without the {}, as it's not a consumable it shouldn't be necssary.
That's what I had originally; it doesn't make any difference. I suppose
I should just grovel the code if you think the behaviour is wrong.
>> serial jobs with -l h_rt=432000 will run for all users, but parallel
>> ones won't for users not in the ACL (due to that limit according to
>> qstat). Two slots with half the h_rt will run.
By the way, the documentation for {} in a limit is pretty obscure, and I
think it should be re-written, as I meant to say before:
By default, the expressed limit counts for the entire filter scope.
To express a filter-scope-specific limit, it's possible to define an
expanded list by setting the list between '{' '}'. It's only possible
to set one complete filter in an expanded list.
Is the description of {} as meaning `for each', as opposed to `for all',
a good way to put it?
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
