understandable.

bug 2496

src/common/mapping.h was the one place outside of slurm/*h that used this,
just remove it from there.

Replace macro with #ifdef __cplusplus in slurm/*h in case anyone is linking
C++ against libslurm.

If your compiler is so bad it can't produce a useable definition of 'bool',
you're going to have a lot of other problems.

No functional change for anyone without CRAPPY_COMPILER defined.

Macro hasn't been used consistently for three+ years, and is protecting against
compilation by non-ANSI C compilers which has not been a concern for quite some
time. Cleanup formatting of function declarations while here.

No change to logic.

Distribute only the maintained doc/html and doc/man directories.

Reports and notes are a historical artifact that can be found in git
tags if necessary, but have no value for modern installations.

bug 2186

This fixes a bug introduced in commit 52fe3de1
in the event the fork() call fails in slurmstepd.

Insure that a job is completely launched before trying to suspend it.
Previous logic would start suspend logic early in the life of the
slurmstepd process, after it's listening socket was open but before
the tasks were launched. This defers the suspend logic until after
all prologs and setup completes and the tasks are launched. This is
important in the case of gang scheduling, in which newly launched
jobs can be immediately suspended.
bug 2494

commit 75317972.

commit ff2c5b88

ff2c5b88

QOS flag affects.

deal with time limit with TRES limits.

to use this function with associations.

Bug 1976

If power save mode was configured along with PrologSlurmctld, then
when PrologSlurmctld completed, it was clearing the node's PowerUp
state flag, which launched the job before boot completed. New logic
waits for the boot to complete and slurmd to register on the node
before clearing the PowerUp flag.

Previous logic was not waiting for nodes to all go into "on" state

Found with -Werror=old-style-declaration, remove it rather than move
'inline' to the start of the declaration to silence the warning.

Default value is 1. Weight is uint32_t so this check was always succeeding.

Moe noted in 2008 that this was not needed on recent kernels.
Eight years seems like enough time.

Coverity issue 70420.