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)

Conflicts:
	src/slurmctld/job_mgr.c

it turns out SLES 11 SP3 (at least) defines it with a newline, so
this will be a problem for anyone building RPMs on that OS.

Without this patch, jobs with an infinite time limit would have
their preemption GraceTime ignored.

For the salloc, sbatch and srun commands, report usage of the
--signal option when the user requests command help.

related to bug 789

them.

commit 8ddadea5 combined all
pending jobs, even if they had the special exit flag set. This
treats pending and special_exit state jobs differently. Only those
jobs with state pending (and NOT special_exit) are combined in
squeue.

Modify slurmd to use the ChosLoc configuration parameter to
control how slurmstepd is launched.