This is for consistency. All of the other backfill parameters
start with "bf_".

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

Previously slurmctld would restart without information about
allocated ports. This add save/restore logic which will work
for graceful shutdowns. More work is needed in the case of
slurmctld crashes.

bug 607

bug 607

Make job array expressions more flexible to accept multiple step counts in
the expression (e.g. "--array=1-10:2,50-60:5,123").

placed.

Underlying code incomplete. Only added the flag.

accounting if running for the first time (should speed up startup
dramatically on systems with lots of nodes or lots of jobs).

count.

nodes.

select/cons_res bug fix for range of node counts with --cpus-per-task
option (e.g. "srun -N2-3 -c2 hostname" would allocate 2 CPUs on the first
node and 0 CPUs on the second node).

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

variable.

This reverts commit 1764a7e2.

Conflicts:

	NEWS

is not a corresponding association.

is not a corresponding association.

disabled.

Added sbatch '--parsable' option to output only the job id number and the
cluster name separated by a semicolon rather than "Submitted batch job....".
Errors will still be displayed.

needed to forward a message the slurmd would core dump.

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

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