Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
Slurm
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD 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
tud-zih-energy
Slurm
Commits
9d80dca4
Commit
9d80dca4
authored
22 years ago
by
Moe Jette
Browse files
Options
Downloads
Patches
Plain Diff
*** empty log message ***
parent
1f42cbdf
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
doc/man/man1/srun.1
+42
-9
42 additions, 9 deletions
doc/man/man1/srun.1
src/srun/srun.csh
+3
-2
3 additions, 2 deletions
src/srun/srun.csh
with
45 additions
and
11 deletions
doc/man/man1/srun.1
+
42
−
9
View file @
9d80dca4
...
@@ -458,6 +458,17 @@ total number of processes in the current job
...
@@ -458,6 +458,17 @@ total number of processes in the current job
SLURM_NODELIST
SLURM_NODELIST
list of nodes that the slurm job is executing on.
list of nodes that the slurm job is executing on.
.SH "SIGNALS AND ESCAPE SEQUENCES"
Signals sent to the \fBsrun\fR command are automatically forwarded to
the tasks it is controlling with a few exceptions. The escape sequence
\fB<control-c>\fR will report the state of all tasks associated with
the \fBsrun\fR command. If \fB<control-c>\fR is entered twice within
one second, then the associated SIGINT signal will be sent to all tasks.
The escape sequence \fB<control-z>\fR is presently ignored. Our intent
is for this put the \fBsrun\fR command into a mode where various special
actions may be invoked.
.SH "MPI SUPPORT"
.SH "MPI SUPPORT"
On computers with a Quadrics interconnect, \fBsrun\fR directly supports
On computers with a Quadrics interconnect, \fBsrun\fR directly supports
the Quadrics version of MPI without modification. Applications build
the Quadrics version of MPI without modification. Applications build
...
@@ -479,10 +490,35 @@ executing the command \fBsrun /bin/hostname\fR and writing its standard
...
@@ -479,10 +490,35 @@ executing the command \fBsrun /bin/hostname\fR and writing its standard
output to the desired file. Execute \fBmpirun \-\-help\fR for more options.
output to the desired file. Execute \fBmpirun \-\-help\fR for more options.
.SH "EXAMPLES"
.SH "EXAMPLES"
.eo
This simple example demonstrates the execution of the command \fBhostname\fR
in eight tasks. At least eight processors will be allocated to the job
(the same as the task count) on however many nodes are required to satify
the request. The output of each task will be preceeded with its task number.
.br
> srun \-n8 \-l hostname
This example demonstrates how one might submit a script for later
execution (batch mode). The script will be initiated when resources
are available and no higher priority job is pending for the same
partition. The script will execute on 4 nodes with one task per node
implicit. Note that the script executes on one node. For the script
to utilize all allocated nodes, it must execute the \fBsrun\fR command
or an MPI program.
.br
> cat my_script
.br
#!/bin/csh
.br
date
.br
srun \-l hostname
.br
> srun \-N4 \-b my_script
This example demonstrates how one executes a simple MPICH job
This example demonstrates how one executes a simple MPICH job
in the event that
it
has not been configurated to automatically
in the event that
MPICH
has not been configurated to automatically
set the required parameters (
again,
this is the worst cases scenario).
set the required parameters (this is the worst cases scenario).
We use \fBsrun\fR to build a list of machines (nodes) to be used by
We use \fBsrun\fR to build a list of machines (nodes) to be used by
\fBmpirun\fR in its required format. A sample command line and
\fBmpirun\fR in its required format. A sample command line and
the script to be executed follow.
the script to be executed follow.
...
@@ -492,19 +528,16 @@ the script to be executed follow.
...
@@ -492,19 +528,16 @@ the script to be executed follow.
.br
.br
srun /bin/hostname >nodes
srun /bin/hostname >nodes
.br
.br
mpirun -np $SLURM_NPROCS -machinefile nodes /bin/hostname
mpirun
\
-np $SLURM_NPROCS
\
-machinefile nodes /bin/hostname
.br
.br
rm node_list
rm node_list
.br
.br
> srun -N2 -n4 my_script
> srun \-N2 \-n4 my_script
.ec
.eo
If MPICH is configured to directly use SLURM, the execute line is
If MPICH is configured to directly use SLURM, the execute line is
the much simpler:
the much simpler:
.br
.br
> mpirun -np 4 /bin/hostname
> mpirun \-np 4 /bin/hostname
.ec
.SH "BUGS"
.SH "BUGS"
If the number of processors per node allocated to a job is not evenly
If the number of processors per node allocated to a job is not evenly
...
...
This diff is collapsed.
Click to expand it.
src/srun/srun.csh
+
3
−
2
View file @
9d80dca4
#!/bin/csh
#!/bin/csh
@ i = 0
@ i = 0
while ($i < 2000)
while ($i < 200)
./srun -n1 /bin/hostname
./srun -n4 -N1 -O -b tst
sleep 1
@ i++
@ i++
end
end
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