Porting to 17.11 finished; proper freeing of helper msgs, msg pack and unpack functions fixed, some function names were changed i, version 17, signal-based slurmd registration converted to shared memory var based registration

bf_queue_limit parameter added to limit jobs checked in the queue to be backfilled. It is a slurm.conf parameter

Fixed a case of synch in which slurmd was not waiting next second to pass before entering next cycle

Created new fields in job structure, then exported by jobcomp plugin to generate more information about scheduling

MAX_RANGE for maximum number of nodes increased, backfill and normal scheduler statistics, in swf2trace number of tasks equals number of requested CPUs

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

Bug 8084.

Stop treating "nobody" as the error condition.

Bug 7845.

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

If this failed, the step would launch as root instead of the desired
user, which could be exploited.

Bug 8084.

CVE-2019-19728.

Bug 8084.

Encourage the use for restricted permissions for slurmdbd.conf since
this file will contain your MySQL username and password on most systems.

CVE-2019-19727.

Bug 7379

Signed-off-by: Brian Christiansen <brian@schedmd.com>

Bug 7861

Bug 7291

Bug 7291

In a multi-cluster environment a job may submit more jobs as part of
its workflow. This fixes situations where the variable is inherited
incorrectly on sub-jobs.

Bug 7998

srun waits for the prolog to finish before launching a job step.
In _is_prolog_finished(), slurmctld checks the state reason:

	if (job_ptr) {
		is_running = (job_ptr->state_reason != WAIT_PROLOG);
	}

But if the job is updated during the job prolog, then _update_job() will
change the state_reason, and then slurmctld will tell srun that the
prolog is completed even if it isn't. If srun launches a job step before
the extern sets up x11, then the job step won't have x11 information. To
fix this, don't change state_reason in _update_job() if it equals
WAIT_PROLOG.

Bug 7525