Since ReleaseAgent is no longer required, we can strip out
all the supporting logic for it.

Statically linked Cray PMI applications still expect to use some file paths
containing the old SLURM_ID_HASH format. Some Cray customers have
certification requirements that make recompilation difficult.

The attached patch defines a macro to convert the new SLURM_ID_HASH
to the old format, and writes the files and symlinks necessary for statically
linked Cray PMI applications to work.

Bug 4114

Bug 4094

Ensure proper termination in places that were otherwise missing
it, and remove some awkward termination handling in other locations.

Starting from glibc-2.25 the macros major and minor are only available
from sys/sysmacros.h. This patch uses an autoconf macro to detect the
location and includes the header accordingly.

Bug 3982.

just unfreed memory, no real concern.

Fix regression in commit e5c05549 that would put the stepd pid into the memory cgroup instead of the task's pid.

Beforehand this would put the result of getpid() into the cgroup.  Before
e5c05549 this was done in the child of the fork which would get you
the task's pid, but moving it to run in the parent broke this logic.

What this patch does is adds pid to the input parameters of
task_g_pre_launch_priv making it so we could use the correct pid.

Makes testing with multiple-slurmd much nicer.

An array was only being partially cleared due to bad logic
bug 3876

Bug 3874.

cpus on the node.

end at the same time.

Bug 3604.

This reverts commit 003cd84c.

bug 3379

Task/cray: Treat missing "mems" cgroup with "debug" messages rather than
    "error" messages. The file may be missing at step termination due to a
    change in how cgroups are released at job/step end.

Bug 3447

FreeBSD requires this to build; overlooked in 2d9e999f.

PATH_MAX is used in many other places within the source without these
definitions; while technically optional in POSIX1.2008 I have not
seen anywhere that does not set it, and if such a system exists
it'll be needed elsewhere and the build system should handle it.

Also, POSIX1.2008 states this must be at least 1024, not 256
as used here.

Bug 3364.

Bug introduced yesterday in commit 239cfa96

Several possibly unterminated string operations
Several memory leak fixes

Covert bitstring.c to use it instead of BITSTR_SINGLE_FMT and
BITSTRING_RANGE_FMT and remove those.

Use within task/affinity as well so that builds with
USE_64BIT_BITSTR enabled will pass.

Missed the extra comma this introduces; looking at alternate approaches.

This reverts commit 58cd45ae.

Use within dist_tasks.c when printing a bitoff_t to fix compile with
USE_64BIT_BITSTR enabled.

Revise commit e6ef1f0c
The root cause of the failure is a bug in HWLOC that has since
been fixed in HWLOC version 1.11.5.

task/cgroup - Change error message if CPU binding can not take place to
    better identify the root cause of the problem. Specifically, if
    the hwloc_get_obj_below_by_type() function call completely fails
    that is likely due to task/affinity not being configured, so
    cpusets are not configured. Previous message was
    "task/cgroup: task[%u] infinite loop broken while trying to provision compute elements using %s (bitmap:%s)"
    The new message is
    "task/cgroup: hwloc_get_obj_below_by_type() failing, task/affinity plugin also required"