On Thursday, 20 September 2018 1:50:39 AM AEST Siddharth Dalmia wrote:
> Is it possible to have a separate timeout for interactive jobs? Or can
> someone help me come up with a hack to do this?
I believe you should be able to catch interactive jobs in the submit filter by
looking for the absence
Hi,
We also have multiple partitions, but in addition we use a job submit
plugin to distinguish between srun/salloc and sbatch submissions. This
plugin forces a specific partition for interactive jobs (and the timelimit
with it) and using the license system it limits the number of simultaneous
int
I don’t. If they want to submit a job running ‘bash’ at the same priority as a
regular batch job shell script, that’s on them. If and when we go to an
accounting model based off reserved resources and time, it’ll handle itself.
On Sep 19, 2018, at 11:54 AM, Siddharth Dalmia
mailto:dalmia@gm
Thanks for your response Mike. I have a follow-up question for this
approach. How do you restrict someone to start an interactive session on
the "batch" partition?
On Wed, Sep 19, 2018 at 12:50 PM Renfro, Michael wrote:
> We have multiple partitions using the same nodes. The interactive
> par
We have multiple partitions using the same nodes. The interactive partition is
high priority and limited on time and resources. The batch partition is low
priority and has looser time and resource restrictions.
And we have a shell function that calls srun —partition=interactive —pty $SHELL
to m
