- Previously long paths/filenames were truncated at 256 characters.
  Use PATH_MAX instead.
- Function previously truncated the executable name at the first
  space character during own string copy function. Replace with
  strlcpy.
- Refactor to remove extraneous temp variables, use strlcpy
  instead of snprintf, getenvp instead of local env parser.

Cray/capmc_resume script modify a node's features (as needed) when the
    reinit (reboot) command is issued rather than wait for the nodes to change
    to the "on" state. This will insure the correct node features in the event
    the capmc_resume script times out or otherwise fails before the nodes come
    back up.
bug 2832

bug 2582

The slurm_get_auth_info() function returns an xmalloc'ed string
which few places were xfree'ing. The function in the past did
not xmalloc a value, but returned a pointer to a cached string.
When that was changed, the calls to the function were not all
changed, resulting in leaks if AuthInfo was defined in slurm.conf.

it.

This reverts commit 7843e158.

Conflicts:
	NEWS

Recalculate a job's memory allocation after node reboot if job requests all
    of a node's memory and FastSchedule=0 is configurated. Intel KNL memory size
    can change on reboot with various MCDRAM modes.
bug 2822

Prior logic was getting confused with NUMA containing no cores.
bug 2745

doesn't have a parent.

This adds support for burst buffer re-issue of pre-load operation
when slurmctld restarts with job in configuring state. Also copy
NEWS item to v16.05.

Prevent job stuck in configuring state if slurmctld daemon restarted while
    PrologSlurmctld is running.
bugs 2789 and 2810

can work on a BGAS node.

Bug 2806

of continuously printing the message over and over as the problem will
most likely not resolve itself.

Bug 2797

Prevent job stuck in configuring state if slurmctld daemon restarted while
    PrologSlurmctld is running.
bugs 2789 and 2810

can work on a BGAS node.

Bug 2806

of continuously printing the message over and over as the problem will
most likely not resolve itself.

Bug 2797

account or wckey.

Fix for tracking job resource allocation when slurmctld is reconfigured
    while Cray Node Health Check (NHC) is running. Previous logic would fail to
    record the job's allocation then perform release operation upon NHC
    completeion, resulting in underflow error messages.
bug 2353

While here, mark options const, and add leading underscore to denote this
as a static function (only called within hostlist.c). Also change strcmp
to xstrcmp.

Commit a6ffef22 changed this function and would alter the input hn,
which led to subsequent calls to the function having wrong prefix
lengths for that hostrange precluding it from matching correctly.

Bug 2558.

and error files.

The buffer to be used for reading the system /proc/*/stat files
is moved from the stack to the heap (i.e. malloc'ed memory) and
initialized to zero, and increased in size from 1k to 4k.
I don't see how this could make any difference, but this anomaly
was reported by valgrind.
bug 2234

The #define of SLURMSTEPD_MEMCHECK in src/slurmd/common/slurmstepd_init.h
must be changed to enable memcheck or valgrind. Also change a #if in
src/slurmd/slurmd/req.c near where you find the "valgrind" references.
Bug 2334 diagnostics

If the QOS includes a time limit, skip checking the partition limit.
The QOS limit is checked separately elsewhere.

'the the' is is a a mistake mistake.

Wrong order of operations results in the return code being 0/1.

Fix for "scontrol -dd show job" with respect to displaying the specific
    CPUs allocated to a job on each node. Prior logic would only display
    the CPU information for the first node in the job allocation.
Bug introduced in commit 0f826c0b
due to misplaced parenthesis

Wrong order of operations results in the return code being 0/1.

If the plugin ever returns an error the variables weren't initialized so
when they were freed they could corrupt memory.

Bug 2790

Hi, before I never tried to set pmix plugin as the default in the slurm.conf.
Setting it in my new test installation highlighted the subject problem.
bug 2786

Bug 2787