Conflicts:
	NEWS

Conflicts:
	META

This bug was introduced yesterday in commit
6cb722dc

If the prolog container creation call (PrologFlags=contain) was
in progress when a job termination RPC arrived at the slurmd,
the slurmstepd and sleep processes could be orphaned until the
slurmd restarted.

The test program seems to have been using the wrong time functions
and failing. Including time.h fixed the problem.

Looks like this should of happened in 3d4ff78e

Bug 1679

Mostly dead stores.
One bad index in job accounting for TRES.
one bad index in slurmd memory limit per CPU calculation

Fix systemd startup files to use default values for pid files

Conflicts:
	src/plugins/switch/cray/util.c

switch/cray: Revert logic added to 14.11.6 that set "PMI_CRAY_NO_SMP_ENV=1"
if CR_PACK_NODES is configured.
bug 1585

If the job step created for external processes (with "PrologFlags=contain")
lacks any accumulated resource use, then don't notify the slurmctld
of completion. This change eliminates an RPC which has no meaningful
data.

Change some job step ID references:
from NO_VAL to SLURM_BATCH_SCRIPT and
from INFINITE to SLURM_EXTERN_CONT

No real change to logic

preempt/job_prio plugin: Implement the concept of Warm-up Time here. Use
the QoS GraceTime as the amount of time to wait before preempting.
Basically, skip preemption if your time is not up.