Update slurm.spec and slurm.spec-legacy as well.

Would cause an unexpected reversion to 19.05.0 behavior if a QOS has
UsageFactor != 0 and any combination of flags set.

Bug 7215.

Update slurm.spec and slurm.spec-legacy as well.

Update slurm.spec and slurm.spec-legacy as well.

Use safe_unpackstr_xmalloc() instead of unpackstr_ptr to ensure all
strings are escaped correctly in SlurmDBD.

This requires the introduction of the _free_local_*() functions to free
the structure members, whereas they were previously just pointers into
the single managed buffer which was cleaned up elsewhere.

Remove the unsafe unpackstr_ptr macro definition as well while here.

CVE-2019-12838.

As well as burst_buffer/cray -> burst_buffer/datawarp.

Bug 7294.

Bug 7294.

Bug 5213

Instead of rejecting a reservation update, create the reservation to
avoid return an error to slurmctld at which point it is too late to do
anything to fix the issue.

Bug 7155.

Wraps logic added in 43ef4f75 to apply UsageFactor at
submission/scheduling. Default is not to.

Bug 7215

Needed to maintain compatibility with OpenMPI's mpirun/mpiexec
launch commands.

Bug 7191.

Bug 7351.

Bug 7351.

Bug 7351.

Bug 7351.

Bug 7351.

Bg 7351.

Bug 7334.

Bug 7337.

Slurm's xmalloc() internally always returns NULL on 0-sized allocations,
and this autoconf macro causes problems building with AddressSanitizer.

Bug 7180.

Remove the need to stop the slurmds.

Continuation of 9cdc8a82

Bug 7135

Bug 7330.

Add explicit support for BOOT_FAIL.
Rearrange db queries for "finished" states assuming -S and -E are
correctly set, as with the other states.
Add error() message to dbd if unsupported state is requested.
Add _supported_state() to the client and fatal() if unsupported state
is requested by the user of the client.

Bug 7110

Bug 7213

should override the real.

Test39.18 was failing by gathering real gpus erroneously.

Flags are stored in a smallint, which can only hold the first 16 bits
worth out of 32 bits of flags currently in use.

MySQL's overflow rules will treat any value > 0xffff as 0xffff, rather than
dropping the higher-order bits (flags), which means the stored value not
only loses the higher-order bits but corrupts the lower-order as well.

The 19.05 release extends the column to bigint (64 bit).

Bug 6969.

if OverTimeLimit is Unlimited.

Bug 6093

Copied from cons_res commit 8c919742

Bug 7146.

Bug 7146.

Bug 7249.

Bug 7249.