Otherwise non-FairTree systems will have a decay period delay before
the updated value makes it into the sum.

Bug 5202.

Usagefactor matches the documentation and now multiplies TRES time
limits and usage.

Bug 5435

This is very coarse-grained locking, but as the initial implementation
did not anticipate concurrent access this is the safest approach for now.

Bug 5638.

Rather than repeat the #ifdef block through five locations, use a common
function to handle this and print a consistent error message if there
is an issue.

From getrlimit(2):
	setrlimit() now returns with errno set to EINVAL in places that
	historically succeeded. It no longer accepts "rlim_cur =
	RLIM_INFINITY" for RLIM_NOFILE. Use "rlim_cur = min(OPEN_MAX,
	rlim_max)".

(This was causing spurious error messages to appear for sbatch/srun.)

macOS does not permit the symbol overloading trick that was previously
used here. Sending function pointers in as part of slurm_opt_t should
work around this.

Avoids a dereference of slurmctld_primary, which is a weak symbol,
and is not available when the select plugins are loaded in the user
commands.

(Weak symbols on macOS cannot have local definitions as well - so
any reference to them that does not resolve causes the process to
crash.)

macOS always has these available without setting -pthread, and ACX_PTHREAD
does not work properly on macOS at the moment.

These should ideally be split off from the task plugin interface since
they're tied to a specific implementations.

And the core_spec code itself does not really belong directly in
slurmd.c.

There is no equivalent to cpuset_t.

Remove initializations - these are not permitted on weak_import'd
symbols.

This was cobbled together from a few different references.
All it's doing is forcing a symbol to be created with the slurm_*
name, and setting the symbol address to that of the unaliased symbol.

Bug 3745.

Using an index value equal to the number of elements puts you one past
the end of the array, modify conditional to >= instead.

CID 197759.

Anyone jumping to the cleanup label does not have agent_info_ptr set.

CID 197735.

Bug 6513

Bug 6513

Bug 6513

Bug 6513

CID 197758.

I believe job cannot be NULL here, but the flow through this function is
messy, and relies on some external setup that has not been documented with
xassert()s. Put this in for now as a stop-gap; this code should be
refactored at a later point.

Bug 6632.

The slurmsmwd cannot be build as part of a Cray Aries build at this time,
so should not be bundled alongside it. Add this separate build option to
make it easier to package independently of the main installation.

Bug 6632.

The --disable-native-cray option was used to revert back to Cray/ALPS mode,
and does not do anything at this point. So reuse the spec option to actual
disable ("Native") Cray Aries builds.

Bug 6632.

when one offset passes and other fails.

Bug 6892

Bug 6513.

Bug 6513