LIBS can have a previous value, as depicted in ./configure --help

"Some influential environment variables:
(...)
 LIBS        libraries to pass to the linker, e.g. -l<library>
"
Original assignation to LIBS overwrites this value. With this edition, the user defined flags and NCURSES ones are both employed by the linker.

This matches the documentation

Capture MCDRAM percentages for various configurations from capmc.
This assumes the percentages for various configurations will be
identical for all nodes within a cluster.

clang found a deferencing null issue which lead to finding the parsing error.

Added new job dependency type of "aftercorr" which will start a task of a
    job array after the corresponding task of another job array completes.
bug 2460

In particular, it seems that MariaDB has changed the default for
innodb_lock_wait_timeout has been lowered which can cause issues
for the various rollup processes on systems with high job counts.

Fix some timing issues with respect to rebooting a node, especailly
KNL node needing reboot to change configuration.

would only track gres/gpu, now it will track both gres/gpu and
gres/gpu:tesla as separate gres if configured like
AccountingStorageTRES=gres/gpu,gres/gpu:tesla

--gres=gpu:tesla

before you needed to give a count

--gres=gpu:tesla:1

now both should work.

Step GRES value changed from type "int" to "int64_t" to support larger
values.

Signed-off-by: Danny Auble <da@schedmd.com>

These changes apply to both the main scheduling logic and backfill
scheduler. If some SchedulerParameters value was configured, the
slurmctld started, then completely removed, and slurmctld reconfigured
the value would not be reset to it's default value but the originally
configured value would persist until slurmctld restarted.

Continuation of 31225a82

Harden code to not fail if node_bitmap passed to _update_node_gres()
has no bits set.

Bug 2430

This may be helpful for timing purposes. Added by Cray request.

Unless a job is running in --multi-prog mode, modify the logic to
resolve the job's path once rather than once for each task. This
may slightly improve performance (requested by Cray).

of it's very close version.

We want to introduce a new behavior in the way slurmd uses the
HealthCheckProgram. The idea is to avoid a race condition between the
first HealthCheckProgram run and the node accepting jobs. The slurmd
daemon will initialize and then loop on HealthCheckProgram execution
before registering with slurmctld. It will stay in this loop until
the HealthCheckProgram returns successfully (the node is still DOWN).

On our clusters we are using NHC as an HealthCheckProgram. NHC drains
the node if it fails and remove the drain if it is successfull, this
behavior fits well with our purpose. This behavior permits us to start
slurmd at boot without setting up a complex boot sequence in the init
system, slurmd just wait for the node to be ready before registering.

The HealthCheckProgram is not run during slurmd startup if
HealthCheckInteval is 0.

Bug 2507

Step GRES value changed from type "int" to "int64_t" to support larger
values. Previous logic could fail in step allocation values over 32-bits.
Other GRES values are 64-bit.

slurmstepd to close potential open ones.

It was pointed out the slurmd using acct_gather_energy/ipmi links to
freeipmi which could possibly open /dev/ipmi0 without the close on exec
flag set as root while launching a step leaving it open in the users app.

What this does is sets the flag on the first 256 to mitigate the concern.

Reported by Maksym Planeta.

Bug 2506