jobs happen to be running on blocks not in the new config.

salloc/mpirun does not play well together with task affinity socket binding.  The following example illustrates the problem.

[sulu] (slurm) mnp> salloc -p bones-only -N1-1 -n3 --cpu_bind=socket mpirun cat /proc/self/status | grep Cpus_allowed_list
salloc: Granted job allocation 387
--------------------------------------------------------------------------
An invalid physical processor id was returned ...

The problem is that with mpirun jobs Slurm launches only a single task, regardless of the value of -n. This confuses the socket binding logic in task affinity.  The result is that task affinity binds the task to only a single cpu, instead of all the allocated cpus on the socket.  When mpi attempts to bind to any of the other allocated cpus on the socket, it gets the "invalid physical processor id" error. Note that the problem may occur even if socket binding is not explicitly requested by the user.  If task/affinity is configured and the allocated CPUs are a whole number of sockets, Slurm will use "implicit auto binding" to sockets, triggering the problem.
Patch from Martin Perry (Bull).

Conflicts:
	NEWS

block from the database.

Update reservation web page to describe mechanism to reserve CPUs rather than whole nodes and provide an example.

before we do.

Avoid clearing a job's reason from JobHeldAdmin or JobHeldUser when it is
otherwise updated using scontrol or sview commands. Patch based upon work
by Phil Eckert (LLNL).

Do not remove the backup slurmctld's pid file when it assumes control, only
when it actually shuts down. Patch from Andriy Grytsenko (Massive Solutions
Limited).

during runjob.  The controller isn't notified just yet since the rpc hasn't
been created yet.

be flushed out, it is a no-op now.

Conflicts:
	META
	NEWS

variable wasn't initialized in the job structure making it so that job
wouldn't run.

Conflicts:
	NEWS
	src/sview/common.c

(i.e. BP List -> MidplaneList).

This reverts commit 862fc2b2.

cables. (Round 1)  This code sets things up to handle future changes when
a cable goes down.

algorithm.  The improves timing in the worst cases and simplifies the code
greatly.

for loops.

to use the coordinates instead (much faster).

commented out code, and the FIXME.