Used job terminations due to failure to boot it's allocated nodes
or BlueGene block.
bug 213

This is a correction of a bug introduced in commit
https://github.com/SchedMD/slurm/commit/ac44db862c8d1f460e55ad09017d058942ff6499
That commit eliminated the need of reading the node state information
from squeue for performance reasons (mostly for large parallel systems
in which the Prolog ran squeue, which generates a lot of simultaneous
RPCs, slowing down the job launch process). It also assumed 1 CPU per
node. If a pending job specified a node count of 1 and a task count
larger than one, squeue was reporting the node count of the job as
the same as the task count. This patch moves that same calculation
of a pending job's minimum node count into slurmctld, so the squeue
still does not need to read the node information, but can report the
correct node count for pending jobs with minimal overhead.

to avoid it thinking we don't have a cluster name.

to avoid it thinking we don't have a cluster name.

%o and %Z respectively

If there are completing jobs, a reconfigure will set wrong job/node
state: all nodes of the completing job will be set allocated, and the
job will not be removed even if the completing nodes are released. The
state can only be restored by restarting slurmctld after the completing
nodes released.

Added boards_per_node, sockets_per_board, ntasks_per_node,
ntasks_per_board, ntasks_per_socket, ntasks_per_core, and nice.

This makes it consistent with the value of default_queue_depth.
The backfill scheduler should be able to easily handle this value
(or much higher for pretty much any configuration).

could end up before the job started. Bug 371

This function can now be called to test for processes which are
dumping in order to avoid sending them a SIGKILL until dump
completes. Change in logic required for job_container/cray.

plugins more maintainable.

This avoids waiting for the job's initiation to fail.

Fix job state recovery logic in which a job's accounting frequency was
not set. This would result in a value of 65534 seconds being used (the
equivalent of NO_VAL in uint16_t), which could result in the job being
requeued or aborted.

Problem reported by BYU. slurm.conf included a file one byte in
length. Logic created a buffer one byte long and used fgets()
to read the file. fgets() reads one byte less than the buffer
size to include a trailing '\0', so it fails to read the file.

This problem was reported by Harvard University and could be
reproduced with a command line of "srun -N1 --tasks-per-node=2 -O id".
With other job types, the error message could be logged many times
for each job. This change logs the error once per job and only if
the job request does not include the -O/--overcommit option.

was down (slurmctld not running) during that time period.

version of Slurm.

the reverse of this comment to return the code to the mix.

Visible only using "scontrol show job" today and these fields are
only relevant for batch jobs.

Add mechanism for job_submit plugin to generate error message for srun
salloc or sbatch to log. New argument added to job_submit function in
the plugin.
bug 278

with a vertical bar separating each field.