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
eb21dc61
Commit
eb21dc61
authored
13 years ago
by
Morris Jette
Browse files
Options
Downloads
Patches
Plain Diff
Update cray documentation
parent
5e3db1b2
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/html/cray.shtml
+20
-7
20 additions, 7 deletions
doc/html/cray.shtml
with
20 additions
and
7 deletions
doc/html/cray.shtml
+
20
−
7
View file @
eb21dc61
...
...
@@ -339,13 +339,27 @@ node/31:# emacs -nw /etc/pam.d/common-session
An example of building and installing SLURM version 2.3.0 is shown below.</p>
<p><b>NOTE:</b> By default neither the <i>salloc</i> command or <i>srun</i>
command wrapper can be executed as a background process. This is done in order
to better identify every process spawned under the <i>salloc</i> process by
using terminal foreground process group IDs. You can optionally enable
<i>salloc</i> and <i>srun</i> to execute as background processes by using the
configure option <i>"--enable-salloc-background"</i>, however doing so will
command wrapper can be executed as a background process. This is done for two
reasons:</p>
<ol>
<li>Only one ALPS reservation can be created from each session ID. The
<i>salloc</i> command can not change it's session ID without disconnecting
itself from the terminal and its parent process, meaning the process could not
be later put into the foreground or easily identified</li>
<li>To better identify every process spawned under the <i>salloc</i> process
using terminal foreground process group IDs</li>
</ol>
<p>You can optionally enable <i>salloc</i> and <i>srun</i> to execute as
background processes by using the configure option
<i>"--enable-salloc-background"</i>, however doing will result in failed
resource allocations
(<i>error: Failed to allocate resources: Requested reservation is in use</i>)
if not executed sequentially and
increase the likelyhood of orphaned processes.</p>
<!--Example:
<!-- Example:
Modify srun script or ask user to execute "/usr/bin/setsid"
before salloc or srun command -->
<!-- Example:
salloc spawns zsh, zsh spawns bash, etc.
when salloc terminates, bash becomes a child of init -->
...
...
@@ -355,7 +369,6 @@ login: # slurm/configure \
--prefix=/opt/slurm/2.3.0 \
--with-munge=/opt/slurm/munge/ \
--with-mysql_config=/opt/cray/MySQL/5.0.64-1.0000.2899.20.2.gem/bin \
--enable-salloc-background \
--with-srun2aprun
login: # make -j
login: # mkdir install
...
...
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