Colas,

I would do something like:

sacctmgr modify account where account=<account> user=<user> set
GrpTresRunMins=cpu=0

to unset:

sacctmgr modify account where account=<account> user=<user> set
GrpTresRunMins=cpu=-1

Hope it helps,

Barry


On Thu, Aug 31, 2017 at 10:31 AM, Colas Rivière <[email protected]>
wrote:

>
> Hello,
>
> I contacted a user about some issues with his jobs and would like to lock
> his account until he gets back to me.
> Is it possible to prevent a user from submitting new jobs, or prevent the
> user future jobs to be scheduled?
> I already held his queued jobs and suspended the running ones (with
> `scontrol hold` and `scontrol suspend`), but am concerned about new ones.
> Or is there a better way to handle this?
>
> Thanks,
> Colas
>



-- 
Barry E Moore II, PhD
E-mail: [email protected]

Assistant Research Professor
Center for Simulation and Modeling
University of Pittsburgh
Pittsburgh, PA 15260

Reply via email to