Re: [Condor-users] accounting groups question

[Matthew Farrellee <matt@xxxxxxxxxx>]

Have a look at the group accounting and quota section of the manual...

http://www.cs.wisc.edu/condor/manual/v7.5/3_4User_Priorities.html#25895

@engin.umich.edu isn't a group, it's the UID_DOMAIN of the Schedd where the jobs were submitted.

Best,


matt

On 02/26/2010 07:55 AM, Mag Gam wrote:
> Thanks Matt
> 
> condor_config_val -dump |  egrep 'UID_DOMAIN|FILESYSTEM_DOMAIN'
> FILESYSTEM_DOMAIN = engin.umich.edu
> UID_DOMAIN = engin.umich.edu
> 
> If I do
> 
> condor_userprio -all
> 
> I get the following
> User Name                           Priority  Priority    Factor
> Used  Usage (hrs)    Start Time       Usage Time
> ------------------------------      --------- -------- ------------
> ----  ----------- ---------------- ----------------
> nuh@xxxxxxxxxxxxxxx                 2.53     2.53         1.00    0
>    268.71  2/24/2010 14:19  2/25/2010 15:36
> y2ra@xxxxxxxxxxxxxxx                   2.93     2.93         1.00    7
>        70.98  2/25/2010 21:27  2/26/2010 07:47
> som21@xxxxxxxxxxxxxxx               3.94     3.94         1.00    0
>     57.99  2/24/2010 16:06  2/26/2010 06:17
> fi8abios3@xxxxxxxxxx           4.19     4.19         1.00    0
> 203.20  2/24/2010 19:05  2/25/2010 16:08
> semour@xxxxxxxxxxxxxxx               5.19     5.19         1.00   10
>     285.56 11/16/2009 13:58  2/26/2010 07:47
> 
> 
> I didn't setup ANY accounting groups but it seems condor_userprio
> automatically adds a user to a group.
> 
> So, can I just do
> groups = nuh, yra, som21, fi8abios3, semour
> GROUP_yra = 25
> GROUP_som21 = 25
> GROUP_fi8abios3 = 25
> 
> 
> 
> 
> 
> 
> On Wed, Feb 24, 2010 at 5:40 AM, Matthew Farrellee <matt@xxxxxxxxxx> wrote:
>> On 02/24/2010 08:02 AM, Mag Gam wrote:
>>> We us accounting groups to place quotas on about 300 members of our
>>> research staff. I was wondering if there is a way to prevent a user
>>> from using another group's quota in their submit file. Also, do
>>> accounting groups support wild cards, like:
>>>
>>> *@mich.edu=25
>>>
>>> This will let anyone from mich.edu domain run only 25 jobs?
>>>
>>>
>>> TIA
>>
>> You have to control access to condor_submit if you want to control setting AccountingGroup.
>>
>> mv condor_submit condor_submit.sto
>> cat >> condor_submit << EOF
>> #!/bin/sh
>> condor_submit $* -a +AccountingGroup="$(special_lookup $USER)"
>> EOF
>>
>> Of course, the clever user will just call condor_submit.sto, and to those users you enact social policy. Compare AccountingGroup vs Owner on jobs in the queue or history file and track people down.
>>
>> *@mich.edu isn't a valid AccountingGroup. You set the AccountingGroup to mich_edu.user at submit time for all your @mich.edu users.
>>
>> Best,
>>
>>
>> matt
>>