The logic is only an example and not meant for actual use.

built.

of the current day.

the user commands.

the allocation to 1 instead of 0 which prevents the allocation to happen.

Old functions were completely wrong, but not used on most systems

Old logic uses some vestigial power management logic that no longer
applies. It creates a job allocation, but the job step blocks
indefinitely.

since left the system.

to compile correctly on newer compilers

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

If job involved in dependency completes and is purged the logic
used to test for circular dependencies can use the invalid pointer
and generate an invalid memory reference before the pointer is
cleared from the dependency list data structure.

Without this change, allocations less than a whole node can result
in an incorrect task binding for power7 processors

Without this change, the testing only happens with task/affinity

This bug was introduced in 2.5.2 for the case where a GPU count was
configured, but without device files. Unfortunately it left the
CUDA_VISIBLE_DEVICES environment variable unset if GPUs were configured,
but the job did not request any of them.

This eliminates the need for libnrt.so on the head node.