before ending the job.

will make it so the slurmctld will not signal the apid's in a batch job.
Instead it relies on the rpc coming from the slurmctld to kill the job to
end things correctly.

Refactor scancel so that all pending jobs are cancelled before starting
cancellation of running jobs. Otherwise they happen in parallel and the
pending jobs can be scheduled on resources as the running jobs are being
cancelled.

Add SchedulerParameters option of sched_min_interval that controls the
minimum time interval between any job scheduling action. The default value
is zero (disabled).
bug 1623

Fix some power_save mode issues: Parsing of SuspendTime in slurm.conf was
bad, powered down nodes would get set non-responding if there was an
in-flight message, and permit nodes to be powered down from any state.
bug 1619

Initialize some variables used with the srun --no-alloc option that may
cause random failures.

Also see:
https://github.com/asanchez1987/jobcomp-elasticsearch

job.  This is already handled on the stepd when the script finishes.

often an inventory request is handled.

free afterwards would not have zeroed out memory on the variables that
didn't get unpacked.

sbatch to stop parsing script for "#SBATCH" directives after first command.
It keeps parsing so long as lines contain only white space or comments
(first non-white space character is '#').

Bug 1384

Add SchedulerParameters option of "sched_max_job_start="  to limit the
number of jobs that can be started in any single execution of the main
scheduling logic.

Bug 1601

Bug 1603

and update NEWS

the same time, don't double bill the down time.

database.

Bug 1576

list, but only the column list.

Prevent slurmdbd error if cluster added or removed while rollup in progress.
Removing a cluster can cause slurmdbd to abort. Adding a cluster can cause
the slurmdbd rollup to hang.

Specialized memory (a node's MemSpecLimit configuration parameter) is not
available for allocation to jobs.
Select/linear, cons_res, and serial plugins fixed.
bug 1548

When allocating resources with resolution of sockets, charge the job for a
CPUs on allocated sockets rather than just the CPUs on used cores.