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
a0d1c452
Commit
a0d1c452
authored
17 years ago
by
Moe Jette
Browse files
Options
Downloads
Patches
Plain Diff
Add description of srun Force Terminate message
parent
bdc85810
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/html/faq.shtml
+17
-1
17 additions, 1 deletion
doc/html/faq.shtml
with
17 additions
and
1 deletion
doc/html/faq.shtml
+
17
−
1
View file @
a0d1c452
...
@@ -22,6 +22,7 @@ name for a batch job?</a></li>
...
@@ -22,6 +22,7 @@ name for a batch job?</a></li>
<li><a href="#parallel_make">Can the <i>make</i> command utilize the resources
<li><a href="#parallel_make">Can the <i>make</i> command utilize the resources
allocated to a SLURM job?</a></li>
allocated to a SLURM job?</a></li>
<li><a href="#terminal">Can tasks be launched with a remote terminal?</a></li>
<li><a href="#terminal">Can tasks be launched with a remote terminal?</a></li>
<li><a href="#force">What does "srun: Force Terminated job" indicate?</a></li>
</ol>
</ol>
<h2>For Administrators</h2>
<h2>For Administrators</h2>
<ol>
<ol>
...
@@ -440,6 +441,21 @@ fi
...
@@ -440,6 +441,21 @@ fi
exec screen -S $SCREENSESSION -rd
exec screen -S $SCREENSESSION -rd
</pre>
</pre>
<p><a name="force"><b>16. What does "srun: Force Terminated job"
indicate?</b></a><br>
The srun command normally terminates when the standard output and
error I/O from the spawned tasks end. This does not necessarily
happen at the same time that a job step is terminated. For example,
a file system problem could render a spawned tasks non-killable
at the same time that I/O to srun is pending. Alternately a network
problem could prevent the I/O from being transmitted to srun.
In any event, the srun command is notified when a job step is
terminated, either upon reaching its time limit or being explicitly
killed. If the srun has not already terminated, the message
"srun: Force Terminated job" is printed.
If the job step's I/O does not terminate in a timely fashion
thereafter, pending I/O is abandoned and the srun command
exits.</p>
<p class="footer"><a href="#top">top</a></p>
<p class="footer"><a href="#top">top</a></p>
...
@@ -873,6 +889,6 @@ open file hard limit to 8192 across the cluster.
...
@@ -873,6 +889,6 @@ open file hard limit to 8192 across the cluster.
<p class="footer"><a href="#top">top</a></p>
<p class="footer"><a href="#top">top</a></p>
<p style="text-align:center;">Last modified
6 December
200
7
</p>
<p style="text-align:center;">Last modified
22 February
200
8
</p>
<!--#include virtual="footer.txt"-->
<!--#include virtual="footer.txt"-->
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