Hi Ulf, Sam,
It's maybe worth bearing in mind that just adding users in the fashion
described by Sam may be OK in some cases, but you won't have the ability
to extract statistics on usage of, say, groups or departments. For that
you would need to add accounts (in the Slurm sense of 'bank accounts
I have a script that does more or less what is suggested. I also took an idea
from elsewhere to add accounts for the department (primary GID), assign shares
to that account, and make the members of the department draw their usage from
the parent account. It does then allow other ways to adjust
Hi there,
I use the following cron job that runs every night to add new users:
#!/bin/bash
function usersInGrp {
echo -n $(getent group "$*" | cut -d':' -f 4- | awk -F',' '$1=$1')
}
for user in $(usersInGrp 'cluster.users'; usersInGrp
'ALT_DOMAIN1+cluster.users'; usersInGrp 'ALT_DOMAIN2+
Yes, in a way. In thinking about this for Brown (we haven't implemented it,
yet), we've the idea of having a Linux cron job periodically query the
group membership of the AD group granted access to the HPC resource, and
adding any new users to the SLURM accounting database.
We're at the point of u
Hello,
we think about switch to SLURM. Currently we grant access to the cluster using a active directory group, everyone in this group is allowed to run jobs.
So the users are not known to the SLURM accounting database.
Is it possible to automatically add every new user to an default account
Thanks for confirming the issue.
I found the source of the problem with the help of SchedMD support.
18.08.4 has this bugfix to prevent commands in the cwd from taking
precedence over commands in your PATH:
https://github.com/SchedMD/slurm/commit/ccafaf7b60090155639edcbdbf4a3ab5e36967c6
The
