Skip to content
Snippets Groups Projects
Commit 700fbc1f authored by Thomas Lynn Marcus's avatar Thomas Lynn Marcus
Browse files

make clear that typing `srun` does nothing

parent dc152980
No related branches found
No related tags found
2 merge requests!717Automated merge from preview to main,!715make clear that typing `srun` does nothing and other typos
...@@ -79,7 +79,7 @@ There are three basic Slurm commands for job submission and execution: ...@@ -79,7 +79,7 @@ There are three basic Slurm commands for job submission and execution:
1. `salloc`: Obtain a Slurm job allocation (i.e., resources like CPUs, nodes and GPUs) for 1. `salloc`: Obtain a Slurm job allocation (i.e., resources like CPUs, nodes and GPUs) for
interactive use. Release the allocation when finished. interactive use. Release the allocation when finished.
Using `srun` directly on the shell will be blocking and launch an Executing a program with `srun` directly on the shell will be blocking and launch an
[interactive job](#interactive-jobs). Apart from short test runs, it is recommended to submit your [interactive job](#interactive-jobs). Apart from short test runs, it is recommended to submit your
jobs to Slurm for later execution by using [batch jobs](#batch-jobs). For that, you can conveniently jobs to Slurm for later execution by using [batch jobs](#batch-jobs). For that, you can conveniently
put the parameters in a [job file](#job-files), which you can submit using `sbatch put the parameters in a [job file](#job-files), which you can submit using `sbatch
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment