starts in accounting.

Add an srun shepard process to cancel a job and/or step of the srun process
is killed abnormally (e.g. SIGKILL).

One of our testers discovered a regression in version 2.3.1.  If a job is
pending due to PartitionNodeLimit and the limit is relieved with a
'sacctmgr modify qos name=<qos name> set flags=partitionmaxnodes' new jobs
exceeding the partition limit (but not the QOS limit) are allowed to run.
However, the pending job is never allowed to run.  Attached is a patch to
address this problem.  FYI, this problem doesn't exist in version 2.4.
Patch from Bill Brophy, Bull.

Let a job be submitted even if it exceeds a QOS limit. Job will be left
in a pending state until the QOS limit or job parameters change. Patch by
Phil Eckert, LLNL.

Patch by Alexander Bersenev (Institute of Mathematics and Mechanics, Russia).

There was also some bad code that would reset the conn_type of a block
to SMALL no matter what type of SMALL it was.

This was due to a bug in select/cons_res with some configuration
optiions and job options, especially if there is more than one
thread per core and the job option includes "--threads-per-core=1".
Fixes problem reported by CSCS.

qos on the cluster to fill that in correctly.

incorrectly when getting fairshare from the parent.

Add ReconfigFlags configuration option to control actions of
"scontrol reconfig". Patch from Don Albert, Bull.

wasn't started at the time the eligible message was sent but started
before the db_index was returned information like start time would be lost.

Add numeric range checks to scontrol update options. Patch from Phil Eckert, LLNL.

to use srun instead of runjob.

for this yet though.

Note this is an old bug. The new code keeps slurmstepd alive and it
keeps trying to send step completion message to slurmctld.

Note this is an old bug. The new code keeps slurmstepd alive and it
keeps trying to send step completion message to slurmctld.

This make the same patch to select/linear as Carles Fenoy's patch to
select/cons_res plugin.

Patch 4f68cde5bd6b4fcf839f6694457373c81d9548ba from chaos/slurm by Don Lipari, LLNL

Patch 4f68cde5bd6b4fcf839f6694457373c81d9548ba from chaos/slurm by Don Lipari, LLNL

Backfill scheduling - Add SchedulerParameters configuration parameter of
"bf_res" to control the resolution in the backfill scheduler's data about
when jobs begin and end. Default value is 60 seconds (used to be 1 second).

Do not drain the compute or front-end node when trying to start a job
for which the UID is not found