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
0b6b0897
Commit
0b6b0897
authored
18 years ago
by
Donna Mecozzi
Browse files
Options
Downloads
Patches
Plain Diff
Added an explanation of the items required to configure
PAM to support SLURM (under the UsePAM) option.
parent
279a107f
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/man/man5/slurm.conf.5
+13
-2
13 additions, 2 deletions
doc/man/man5/slurm.conf.5
with
13 additions
and
2 deletions
doc/man/man5/slurm.conf.5
+
13
−
2
View file @
0b6b0897
...
@@ -528,10 +528,21 @@ The defautl value is 50.
...
@@ -528,10 +528,21 @@ The defautl value is 50.
If set to 1, PAM (Pluggable Authentication Modules for Linux) will be enabled.
If set to 1, PAM (Pluggable Authentication Modules for Linux) will be enabled.
PAM is used to establish the upper bounds for resource limits. With PAM support
PAM is used to establish the upper bounds for resource limits. With PAM support
enabled, local system administrators can dynamically configure system resource
enabled, local system administrators can dynamically configure system resource
limits. Changing the upper bound of a resource limit
does
not alter the limits
limits. Changing the upper bound of a resource limit
will
not alter the limits
of running jobs, only jobs started after a change has been made will pick up
of running jobs, only jobs started after a change has been made will pick up
the new limits.
the new limits.
The default value is 0 (not to use PAM).
The default value is 0 (not to enable PAM support).
Remember that PAM also needs to be configured to support SLURM as a service.
For sites using PAM's directory based configuration option, a configuration
file named \fBslurm\fR should be created. The module-type, control-flags, and
module-path names that should be included in the file are:
auth required pam_localuser.so
auth required pam_shells.so
account required pam_unix.so
account required pam_access.so
session required pam_unix.so
For sites configuring PAM with a general configuration file, the appropriate
lines (see above), where \fBslurm\fR is the service-name, should be added.
.TP
.TP
\fBWaitTime\fR
\fBWaitTime\fR
Specifies how many seconds the srun command should by default wait after
Specifies how many seconds the srun command should by default wait after
...
...
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