Re: [slurm-users] Temporary Stop User Submission
On 5/26/23 01:29, Doug Meyer wrote: I always like Sacctmgr update user where user= set grpcpus=0 This GrpCPUs group limit may perhaps affect the entire group? Anyway, GrpCPUs is undocumented in the sacctmgr manual page, for which I opened a bug in https://bugs.schedmd.com/show_bug.cgi?id=16832 I think Sean's suggestion of maxjobs=0 is a better choice, or perhaps set GrpTRES=cpu=0 ? /Ole
Re: [slurm-users] Temporary Stop User Submission
On 5/26/23 01:56, Markuske, William wrote: I would but unfortunately they were creating 100s of TBs of data and I need them to log in and delete it but I don't want them creating more in the meantime. Does your filesystem have disk quotas? Using disk quotas would seem to be a good choice to contain this problem. /Ole
Re: [slurm-users] Temporary Stop User Submission
On 5/25/23 4:16 pm, Markuske, William wrote: I have a badly behaving user that I need to speak with and want to temporarily disable their ability to submit jobs. I know I can change their account settings to stop them. Is there another way to set a block on a specific username that I can lift later without removing the user/account associations? There are many ways to do this, our way is we set their QOS's to one called "batchdisable" and that QOS has "MaxJobsPerUser=0" set on it. One of the benefits of that is it's easy to see everyone who's been blocked from submitting jobs. All the best, Chris -- Chris Samuel : http://www.csamuel.org/ : Berkeley, CA, USA
