Both the primary and backup need to provide similar ping capabilities.
This implementation - with multiple threads launched in parallel - is
the more advanced one, so start reworking it to be able to use it in
the primary controller as well instead of _ping_backup_controller().

Add a boolean option to indicate whether this is running in the active
controller or the backup. This will control whether all other controllers
are pinged (needed by the primary) or only the higher priority controllers
(as done in the backups).

Bug 5256.

Bug 5651.

The correct syntax is .\" not .\ which was causing these to appear in the
man2html formatted version of the man page. As these options do not and will
not exist in 18.08, remove them rather than re-commenting them with the
correct syntax.

The correct syntax is .\" not .\ which caused these to appear in the man2doc
formatted version of the page by accident.

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

And slurm.spec-legacy. Missed in commit ee281387.

Bug 4771.

Asterisk '*' was being used in 2.4, and replaced with colon ':' in 2.5.
But liense_list_to_string was missed, and was still using an asterisk
until now. Since we've internally used both up until 18.08, license parsing
code will need to respect both delimiters until two versions past 18.08.

Bug 5630.

Will be needed to distinguish between which backup controller is resuming.

Bug 5256.

No changes to RPC yet, identical to prior RPC version.

Bug 5256.

This should solve a clang/scan-build issue.

Bug 5256.

starting.

Bug 5565

Bug 5623

# Conflicts:
#	src/plugins/mpi/pmi2/setup.c

%n or %h in the spool dir.

Bug 5096

By default all devices are allowed and GRES, that are associated with a
device file, that are not requested are restricted.

Leaving the ability to read in the file as a contribution is under
review that extends the cgroup_allowed_devices_file.

Bug 4771.

Fail early when the layout requirements cannot be satisfied in
_task_layout_lllp_block().

Otherwise step layout calculations will fail, leading to a
"fatal: _task_layout_lllp_block infinite loop"

Bug 5415.

The conditional for handling --overcommit was not sufficient to prevent
other option combinations from using that code path, resulting in
unexpected resource allocation behavior. Correct that to check that
overcommit is enabled.

Bug 5345.

Bug 5379.

This does change a network RPC after 18.08.0rc1, which is best to be
avoided. But other recent changes have already broken RPC compatibility
between what will be 18.08.0, so we might as well land this now.

Bug 5443.

And add into appropriate pack and unpack functions.

And set it in launch_prolog().

In cases when you have a range first and then a single afterwards:

nid00[446-447],nid00392

It only worked correctly if it were reversed like so:

nid00392,nid00[446-447]

No functional change.

No function change here, identical to 17.11 protocol block.

Bug 5524

Basically count was never getting over 3 so none of the "end" code
was ever happening.

# Conflicts:
#	src/slurmctld/fed_mgr.c

running.

Bug 5624