We would like to put limits on interactive jobs (started by salloc) so
that users don't leave unused interactive jobs behind on the cluster by
mistake.
I can't offhand find any configurations that limit interactive jobs, such
as enforcing a timelimit.
Perhaps this could be done in job_submit.lua, but I couldn't find any
job_desc parameters in the source code which would indicate if a job is
interactive or not.
Question: How do people limit interactive jobs, or identify orphaned jobs
and kill them?
Thanks a lot,
Ole
--
Ole Holm Nielsen
PhD, Senior HPC Officer
Department of Physics, Technical University of Denmark
--
slurm-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
