Correct SelectTypeParameters=CR_LLN with job selecition of specific nodes.
Previous logic would in most instances allocate resources on all nodes
to the job.

Correct squeue's job node and CPU counts for requeued jobs.
Previously, when a job was requeued, its CPU count reported
was that of the previous execution. When combined with the
--ntasks-per-node option, squeue would compute the expected
node count. If the --exclusive option is also used, the node
count reported by squeue could be off by a large margin (e.g.
"sbatch --exclusive --ntasks-per-node=1 -N1 .." on requeue
would use the number of CPUs on the allocated node to recompute
the expected node count).
bug 756

req.c: In function ‘_launch_complete_rm’:
req.c:5372: error: array subscript is above array bounds
req.c: In function ‘_launch_complete_add’:
req.c:5328: error: array subscript is above array bounds

The lines are
if (job_id != active_job_id[j]) {

after the for loops in those functions.

If no match is found in the loop, j will be JOB_STATE_CNT and overflow the
array by one.

jobacct_gather/cgroup.

Support SLURM_CONF path which does not have "slurm.conf" as the file name.
bug 803

For a nested batch job (within an salloc, run "sbatch --jobid=$SLURM_JOBID ..."),
report the completing node rank as 0, rather than -1

If a job has non-responding node, retry job step create rather than
returning with DOWN node error.
bug 734

Also correct related documentation

Add force option to all file removals ("rm ..." to "rm -f ...").
bug 673

Completing nodes is removed when calling _try_sched() for a job, which
is the case in select_nodes(). If _try_sched() thinks the job can run
now but select_nodes() returns ESLURM_NODES_BUSY, the backfill loop will
be ended.

Do not resume a job with specialized cores on a node running another job
with specialized cores (only one can run at a time).
bug 792

Fix dead initialization and memory leak in nonstop

Conflicts:
	doc/man/man5/slurm.conf.5

Related to bug 795

Fix sinfo -R to print each down/drained node once, rather than once per
partition. This was broken in the sinfo change to process each partition's
information in a separate pthread.

Conflicts:
	src/sinfo/sort.c

Correct sinfo --sort fields to match documentation: E => Reason,
H -> Reason Time (new), R -> Partition Name, u/U -> Reason user (new)