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
7a40e1b1
Commit
7a40e1b1
authored
22 years ago
by
Moe Jette
Browse files
Options
Downloads
Patches
Plain Diff
Increase JOB_KILL_TIMEOUT from 60 to 300 seconds to permit for writing large
core file.
parent
6cec88f8
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
src/slurmctld/slurmctld.h
+2
-2
2 additions, 2 deletions
src/slurmctld/slurmctld.h
with
2 additions
and
2 deletions
src/slurmctld/slurmctld.h
+
2
−
2
View file @
7a40e1b1
...
@@ -86,8 +86,8 @@
...
@@ -86,8 +86,8 @@
#define PERIODIC_TIMEOUT 60
#define PERIODIC_TIMEOUT 60
/* Release a job's allocation if it does not terminate gracefully in
/* Release a job's allocation if it does not terminate gracefully in
* JOB_KILL_TIMEOUT seconds */
* JOB_KILL_TIMEOUT seconds
, leave time for large core file write
*/
#define JOB_KILL_TIMEOUT
6
0
#define JOB_KILL_TIMEOUT
30
0
/* Pathname of group file record for checking update times */
/* Pathname of group file record for checking update times */
#define GROUP_FILE "/etc/group"
#define GROUP_FILE "/etc/group"
...
...
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