purged from the system if its front-end node goes down.

database, and the job is running on a small block make sure we free up
the correct node count.

This addresses bug 130

with a job running or trying to run on it.

are planning on using the block.  Previously it would fail those jobs
erroneously.

or previous piecemeal method.

Adapted from a patch from Stephen Trofinoff <trofinoff@cscs.ch>

having the realtime server go down over and over again while waiting
for the poll to finish.

host names. Like done elsewhere in SLURM

users/accounts/flags

correctly for current job.

realtime server.

start in the future but is able to run now.

accounting as well.

We've discovered that our implementation of proctrack/cgroups includes
internal threads as well as the process pids so that "scontrol list pids"
shows them as well. The attached patch (courtesy of Matthieu Hautreux)
to 2.4.2 fixes this problem.

running on it are preemptable by scheduling job.

reported some suspended time.

static blocks.

when none are requested.  The Block allocator sets it up temporarily so
this isn't needed.

and a job comes through backfill and can fit on the block without ending
jobs don't set an end_time for the running jobs since they don't need to
end to start the job.

Return ESLURM_NODES_BUSY rather than ESLURM_NODE_NOT_AVAIL error on job
submit when required nodes are up, but completing a job or in exclusive
job allocation.

previous 20 minute time limit.  The previous behavior would fail for
large files 20 minutes into the transfer.