Try adding a default account and then set a limit of 0 jobs on it.
>From memory I think it is grpjobs
This is the maximum allowed jobs this account can have queued.
This requires limits to be enforced in accountingstorageenforce
Or you could simply add the account to the denyaccount list for t
e lua script is preferable.
>
> Kind regards,
>
> Sam
>
> --
> *From:* slurm-users on behalf of
> Yair Yarom
> *Sent:* Wednesday, 7 November 2018 00:58
> *To:* Slurm User Community List
> *Subject:* Re: [slurm-users] Accounting:
imits)
So the lua script is preferable.
Kind regards,
Sam
?
From: slurm-users on behalf of Yair
Yarom
Sent: Wednesday, 7 November 2018 00:58
To: Slurm User Community List
Subject: Re: [slurm-users] Accounting: set default account with no access
Hi,
You c
But isn't that a user association setting and not an account setting? So
I would have to set it for every user/default account association, no?
Technically doable, but definitely more difficult to manage.
Brian Andrus
On 11/6/2018 3:58 AM, Yair Yarom wrote:
Hi,
You can set the maxsubmitjob=
Hi,
You can set the maxsubmitjob=0 on that default account. That should prevent
anyone from using it, but it won't have a specific message like with the
lua plugin. E.g.
sacctmgr update account default set maxsubmitjob=0
Regards,
Yair.
On Tue, Nov 6, 2018 at 12:58 AM Renfro, Michael wrote:
>From https://stackoverflow.com/a/46176694:
>> I had the same requirement to force users to specify accounts and, after
>> finding several ways to fulfill it with slurm, I decided to revive this post
>> with the shortest/easiest solution.
>>
>> The slurm lua submit plugin sees the job descripti
