Add support for SchedulerParameters value of bf_max_job_start that limits
the total number of jobs that can be started in a single iteration of the
backfill scheduler.
bug 607

A test for bf_max_job_user was > rather than >=

Since the QOS priority is 32-bits, base the preemption priority
upon that 32-bit field and ignore the job size.
Variant of commit  a3e74ef2

The job preemption order was based upon the lowest 16 bits of a
QOS priority, but the field holds 32 bits. This uses a value of
0xffff if the QOS priority is higher.

bug 607

placed.

The select_p_resv_test() functions for the select/linear and
select/bluegene plugins were not updated for specifying core
counts per node. The additional argument was not used, but
now the functions are consistent across all of the select
plugins.

count.

nodes.

If a job requires specific nodes and can not run due to those nodes being
busy, the main scheduling loop will block those specific nodes rather than
the entire queue/partition.
bug 595

is not a corresponding association.

is not a corresponding association.

needed to forward a message the slurmd would core dump.

describing that jobs must be drained from cluster before deploying
any checkpoint plugin.

Re-order existing code so that per-cpu memory limits will be
enforce with both cpus_per_task and ntasks_per_node limits.

Properly enforce a job's cpus-per-task option when a job's allocation is
constrained on some nodes by the mem-per-cpu option.
bug 590

This just shuts down the underlying select plugin used by select/cray
in order for it to free all of its allocated memory

bug 586