- 14 May, 2015 4 commits
-
-
Brian Christiansen authored
Bug 1548
-
Brian Christiansen authored
Conflicts: src/common/slurm_protocol_defs.c
-
Brian Christiansen authored
-
Morris Jette authored
Used a value of 3, it should have been a flag, #4
-
- 13 May, 2015 16 commits
-
-
Danny Auble authored
-
Morris Jette authored
-
Morris Jette authored
-
Brian Christiansen authored
-
David Bigagli authored
-
David Bigagli authored
-
David Bigagli authored
-
Morris Jette authored
Need to exec() some process since linuxproc will never signal a process named "slurmstepd"
-
Morris Jette authored
No changes to logic
-
Danny Auble authored
-
Morris Jette authored
This records accounting for the job container created with a PrologFlags option of "Contain" as added in commit fc359331
-
Morris Jette authored
Add PrologFlags option of "Contain" to create a proctrack container at job resource allocation time. At job allocation time, a slurmstepd is spawned on every allocated compute node in which to place external processes (e.g. PAM can place ssh processes into a cgroup). This entity is accounted for and reported by sacct as "<jobid>.extern". Some more testing and development remain, but it mostly works.
-
Brian Christiansen authored
Bug 1627
-
Brian Christiansen authored
-
Brian Christiansen authored
-
Brian Christiansen authored
-
- 12 May, 2015 11 commits
-
-
Morris Jette authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
function.
-
David Bigagli authored
-
Morris Jette authored
-
Danny Auble authored
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
test34.1 was failing with a configuration of PreemptMode=suspend,gang PreemptType=preempt/partition_prio due to changes in commit f8fb79d5 That change appears to no longer be necessary and breaks a valid configuration.
-
- 11 May, 2015 3 commits
-
-
Morris Jette authored
-
Morris Jette authored
This is a special case. This change documents the way Slurm has always worked.
-
Morris Jette authored
Make sure that old step data is purged when a job is requeued. Without this logic, if a job terminates abnormally then old step data may be left in slurmctld. If the job is then requeued and started on a different node, referencing that old job step data can result in abnormal events. One specific failure mode is if the job is requeued on a node with a different number of cores, and the step terminated RPC arrives later, the job and step bitmaps of allocated cores can differ in size generating an abort. bug 1660
-
- 08 May, 2015 6 commits
-
-
Danny Auble authored
TRES stuff
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
Conflicts: src/plugins/accounting_storage/mysql/as_mysql_job.c
-
Danny Auble authored
-
David Gloe authored
Bug 1657
-