Do not drain the compute or front-end node when trying to start a job
for which the UID is not found

Add configure option of "--without-rpath" which builds SLURM tools without
the rpath option, which will work if Munge and BlueGene libraries are in
the default library search path and make system updates easier.

Add support for job allocations with multiple job constraint counts. For
example: salloc -C "[rack1*2&rack2*4]" ... will allocate the job 2 nodes
from rack1 and 4 nodes from rack2. Support for only a single constraint
name been added to job step support.

Add support for GPU memory allocation on Cray systems using SLURM GRES
(Generic RESource) support. Work by Steve Trofinoff, CSCS.

Do not attempt to run HeathCheckProgram on powered down nodes. Patch from
Ramiro Alba, Centre Tecnològic de Tranferència de Calor, Spain.

If job time limit exceeds partition maximum, but job's minimum time limit
does not, set job's time limit to partition maximum at allocation time.

ESLURMD_GID_NOT_FOUND where slurm would be a little over zealous
in treating missing a GID or UID as a fatal error.

block correctly.

Report correct job "Reason" if needed nodes are DOWN, DRAINED, or
NOT_RESPONDING, "Resources" rather than "PartitionNodeLimit".

plugins in the slurmd.

    value for jobs.

Cray - Fix for srun.pl parsing to avoid adding spaces between option and
argument (e.g. "-N2" parsed properly without changing to "-N 2").

Cray: Add support for job reservations with node IDs that are not in
numeric order. Fix for Bugzilla #5.

Prevent job hold by operator or account coordinator of his own job from
being an Administrator Hold rather than User Hold by default.

Prevent slurmctld crashing with divide by zero with a configuration of MaxMemPerCPU=0.

Add a node state flag of CLOUD and save/restore NodeAddr and NodeHostName
information for nodes with a flag of CLOUD. Major update to elastic computing
document.

block happens correctly now.

Add the ability to update a node's NodeAddr and NodeHostName with scontrol.
Also enable setting a node's state to "future" using scontrol.

Major re-write of the CPU Management User and Administrator Guide (web
page) by Martin Perry, Bull.

If a job can not run due to QOS or association limits, then do not cancel
the job, but leave it pending in a system held state (priority = 1). The
job will run when its limits or the QOS/association limits change. Based
upon a patch by Phil Ekcert (LLNL).

booted block. -- pass 1, more work needs to be done.

Prevent associations from being delete if it has any jobs in running,
pending or suspended state. Previous code prevented this only for running
jobs.

Fix bugs in sched/backfill with respect to QOS reservation support and job
time limits. Patch from Alejandro Lucero Palau (Barcelona Supercomputer Center).