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 <dalmia....@gmail.com<mailto:dalmia....@gmail.com>> wrote: 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 <ren...@tntech.edu<mailto:ren...@tntech.edu>> wrote: 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 make it easier to submit interactive jobs. -- Mike Renfro / HPC Systems Administrator, Information Technology Services 931 372-3601<tel:931%20372-3601> / Tennessee Technological University On Sep 19, 2018, at 10:51 AM, Siddharth Dalmia <dalmia....@gmail.com<mailto:dalmia....@gmail.com>> wrote: Hi all, Is it possible to have a separate timeout for interactive jobs? Or can someone help me come up with a hack to do this? Thanks Sid
