Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
hpc-compendium
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
ZIH
hpcsupport
hpc-compendium
Commits
700fbc1f
Commit
700fbc1f
authored
2 years ago
by
Thomas Lynn Marcus
Browse files
Options
Downloads
Patches
Plain Diff
make clear that typing `srun` does nothing
parent
dc152980
No related branches found
No related tags found
2 merge requests
!717
Automated merge from preview to main
,
!715
make clear that typing `srun` does nothing and other typos
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm.md
+1
-1
1 addition, 1 deletion
doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm.md
with
1 addition
and
1 deletion
doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm.md
+
1
−
1
View file @
700fbc1f
...
@@ -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
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment