On Mon, Mar 17, 2014 at 03:07:31AM -0700, Loris Bennett wrote: > > Hi Jens, > > Jens Dreger <[email protected]> writes: > > > Hi! > > > > I'm sure this is easy, but I can't find the solution: how can I > > prevent Slurm from putting new jobs on the queue? Basically I would > > like to disable sbatch/salloc etc. I set MaxJobs=0 for all accounts, > > but jobs are still placed on the queue with 'JobState=PENDING > > Reason=AssociationJobLimit'. I know I could just block access to the > > submit hosts, but I wonder if this can be done at the Slurm level. > > Try MaxSubmitJobs=0
Ah, here we go. Works! Thanks, Jens. > > > Also, is there an easy way to specify that a maintenance reservation > > should start "as soon as possible"? If I give starttime=now, scontrol > > complains "Requested nodes are busy", which is true of course. I'd > > like to start the reservation as soon as the last currently running > > job finishes. > > > > Thanks, > > > > Jens. > -- Jens Dreger Freie Universitaet Berlin [email protected] Fachbereich Physik - ZEDV Tel: +49 30 83854774 Arnimallee 14 Fax: +49 30 83855902 14195 Berlin
