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.

no big deal, but now we get just a bit more memory allocated (4152 over
instead of the 4100 we were previously looking for)

they are a no-opt when they get to the DBD and we would favor having
job completion messages instead of step completion messages if possible.

or previous piecemeal method.

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

Only set memory.memsw.limit_in_bytes to the computed amount of allowed
RAM+Swap when ConstrainSwapSpace=yes in cgroup.conf.
When ConstrainSwapSpace=yes and ConstrainRAMSpace=no, automatically
set AllowedRAMSpace to 100% in order to compute the memsw.limit based
on the allocated memory plus the allowed swap percent. Then use that
limit for both mem and mem+sw limits.

stop the current poll asap.