Updated also some link references as agreed by e-mail with R. Castain.

Continuation of bbfd1890.

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

Logic was backwards before.

Bug 4459.

These tests were failing on a single node cluster

Refactor logging logic to avoid possible memory corruption on non-x86
    architectures.
bug 4469

There are out of memory conditions where spikes of memory usage hit the
limit set. When this happens (failcnt > 0), the Kernel might be able
to reclaim unused pages and the process can continue without oom-killer
actually killing the process. This may or may not result in an app
problem, thus we want to better clarify the message.

A separate bug will track the potential addition of a new feature to
better discern memory limits being hit from oom-killer actually killing
the process. There are mechanisms to register a notifier through the
cgroup.event_control control file, so that the application can be
notified through eventfd when OOM-Killer actually kills the process.

Bug 3820.

Link published to the slurm-users list by Ralph Castain:
https://pmix.github.io/pmix/how-to

only affects current 17.11 users tracking licenses or GRES in the database.

Bug 4553

# Conflicts:
#	src/plugins/accounting_storage/mysql/accounting_storage_mysql.c

increment ids for the tres_table.

Bug 4553

Turns out auto_increment=# doesn't work in MySQL at the time of writing
but does work correctly in MariaDB >=10.2.4+

See bug for more information.

This reverts commit 12794fb0.

increment ids for the tres_table.

Bug 4553

Turns out auto_increment=# doesn't work in MySQL at the time of writing
but does work correctly in MariaDB >=10.2.4+

See bug for more information.

Bug 4555

Bug 4558.

to replace DOWN or DRAINED nodes.

Bug 4537

If running on a single node cluster with an epilog, the delay could
  cause this test to fail

Coverity CID 181852

Bug 4529

Bug 4564

_run_prog() executes after a fork(), if some thread in the parent
was holding slurm_conf_lock() it would never be released, and the
child will deadlocked.

Already fixed for 17.11 by commit e205eeaf, this backports just
the change for _run_prog().

Bug 4562.

The ability to enforce strict content-type checking has existed since
Elasticsearch 5.3 via the http.content_type.required configuration setting.
In 5.x it is optional, and defaults to false, in Elasticsearch 6.0, that
setting defaults to true, and there is no way to disable it.

If required and not appended, Elasticsearch would response with status 406,
so "Content-Type: application/json" is appended from now on. Tested against
Elasticsearch 5.5.1 and 6.1.1.

Bug reported to slurm-users list from E.S. Rosenberg. Patch suggested didn't
check the return code of curl_slist_append() and didn't free the slist.

Bug 4537

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

Bug 4551,4553

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