However, --mem=0 now reflects the appropriate amount of memory in the
system, --mem-per-cpu=0 hasn't changed.  This allows all the memory to
be allocated in a cgroup but is not "consumed" and is available for
other jobs running on the same host.
Eric Martin, Washington University School of Medicine

Correct list of unavailable nodes reported in a job's "reason" field when
that job can not start.
bug 1614

which can be used to aggregate messages to the slurmctld into a single
message to reduce communication to the slurmctld.  Currently only epilog
complete messages and node registration messages use this logic.

bug 1679

Changes some variable names "norelation" to "no_relation"
Replace some blocks of spaces with tabs
Add definition of layouts "free" call to slurm.h.in
Add "layout" information to scontrol help message
Fix typo in error message
Translate a french error message to english "valide" to "valid"

Bug 1679

switch/cray: Revert logic added to 14.11.6 that set "PMI_CRAY_NO_SMP_ENV=1"
if CR_PACK_NODES is configured.
bug 1585

preempt/job_prio plugin: Implement the concept of Warm-up Time here. Use
the QoS GraceTime as the amount of time to wait before preempting.
Basically, skip preemption if your time is not up.

Bug 1548

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.

Bug 1627

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

Bug 1657

Bug 1618

cpu count.

Add re-entrant versions of glibc time functions (e.g. localtime) to Slurm
in order to eliminate rare deadlock of slurmstepd fork and exec calls.
bug 1638

utilization.

random crashing in db2 when the slurmctld is exiting.

Signed-off-by: Danny Auble <da@schedmd.com>

In slurmctld communication agent, make the thread timeout be the configured
value of MessageTimeout (or 30 seconds, whichever is larger) rather than
30 seconds.

Fix scancel bug which could return an error on attempt to signal a job step.
A simple "scancel 12.3" to signal a specific job step would fail. Adding
another option (say "-i", "--partion=", etc.) would fix this.