[Condor-users] Dedicated user accounts for dynamic slots

[Bob Briscoe <paw_deer@xxxxxxxxxxx>]

Hi,

I currently use dedicated accounts for vanilla universe jobs running within static slots, using the DEDICATED_EXECUTE_ACCOUNT_REGEXP approach as described in section 3.3.7 of the manual (I'm using 7.6.6 under Linux), which works fine. However, when experimenting with dynamic slots, I run into the following problem. I first define one partitionable slot for the entire machine, say via:

SLOT_TYPE_1                              = cpus=2, ram=100%, disk=50%, swap=10%
NUM_SLOTS_TYPE_1                  = 1
SLOT_TYPE_1_PARTITIONABLE   = TRUE

If I then keep my dedicated account definitions from the static set up, i.e.

SLOT1_USER                         = condor_user1
SLOT2_USER                         = condor_user2
STARTER_ALLOW_RUNAS_OWNER          = False
DEDICATED_EXECUTE_ACCOUNT_REGEXP   = condor_user[0-9]+

then if I have two jobs running simultaneously, each with just one cpu, then both jobs will appear to belong to condor_user1. I suppose this is not too surprising as the dynamic slots become slot1_1 and slot1_2. If I now try to use the following dedicated account names (in order for slot1_2 to use condor_user2):

SLOT1_1_USER                         = condor_user1
SLOT1_2_USER                         = condor_user2

then these definitions are silently ignored and both jobs run as user "nobody", which is the default for Linux operation without dedicated accounts.

Can anyone spot what I'm doing wrong, and how I can force those dynamic slots to run as different dedicated users?

TIA

Bob