From 24035e0935411eeb3a91a8e2acc87190b76f6a12 Mon Sep 17 00:00:00 2001
From: John Thiltges <jthiltges2@unl.edu>
Date: Wed, 18 Mar 2020 15:34:40 -0500
Subject: [PATCH] On the interactive job page, add notes on default job
runtime, and how to increase it
---
content/submitting_jobs/creating_an_interactive_job.md | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/content/submitting_jobs/creating_an_interactive_job.md b/content/submitting_jobs/creating_an_interactive_job.md
index 1100a049..2d902535 100644
--- a/content/submitting_jobs/creating_an_interactive_job.md
+++ b/content/submitting_jobs/creating_an_interactive_job.md
@@ -15,19 +15,20 @@ Submitting an interactive job is done with the command `srun`.
$ srun --pty $SHELL
{{< /highlight >}}
-or to allocate 4 cores per node:
+or to allocate 4 cores per node for 3 hours:
{{< highlight bash >}}
-$ srun --nodes=1 --ntasks-per-node=4 --mem-per-cpu=1024 --pty $SHELL
+$ srun --nodes=1 --ntasks-per-node=4 --mem-per-cpu=1024 --time=3:00:00 --pty $SHELL
{{< /highlight >}}
Submitting an interactive job is useful if you require extra resources
to run some processing by hand. It is also very useful to debug your
processing.
-And interactive job is scheduled onto a worker node just like a regular
+An interactive job is scheduled onto a worker node just like a regular
job. You can provide options to the interactive job just as you would a
-regular SLURM job.
+regular SLURM job. The default job runtime is 1 hour, and can be
+increased by including the `--time` argument.
### Priority for short jobs
--
GitLab