to avoid overlapping erroneously.

Before you could get overlapping reservations if you asked for a core
based reservation and then a whole node reservation.  This fixes that.

describing the error code.

Test 3.11 was failing in some configurations without this as
the CPU count in the RPC was lower than the number of nodes in
the required node list

MaxProcSecondsPerJob.

error

terminating a job.

and abort the job.

a midplane.

MaxNode limit.

only needs to be called once.

    reference.

s_p_options_t struct.

The CPU specification enforcement is strict rather than advisory.

warning.

of cpus in the job_resources_t structure so as nodes finish the correct
cpu count is displayed in the user tools.

Previous logic would only make available the CPUs associated with
the first N GRES, where N is the number of requested GRES. CPUs
which might be made available by using different GRES were not
considered available.
bug 1092

Eliminate race condition in enforcement of MaxJobCount limit for job arrays.
The job count limit was checked for a job array before setting the slurmctld
job locks. If new jobs were submitted between the test and the job array
creation such that the job array creation would result in MaxJobCount being
exceeded, then a fatal error would result.
bug 1091

message back.  In slow systems with many associations this could speed
responsiveness in sacctmgr after adding associations.

Describe how jobs could be lost on slurmctld crash
Backport MPI performance FAQ
Fix bad href tag