Problems with jobs starting on reserved nodes

Added check for preeption mode before changing time limit to 1 if flag no reserve is enabled, as this can cause a problem with jobs starting on nodes with future reservations.

This bug was introduced on Friday and fails to address an environment
variable not being set

on them.  This should only happen in extreme conditions.

And the user allocation tries to bind to sockets

with associations get the deleted associations as well.

request resources that reach a 'Max' limit.

this is happening because the energy status MSR registers for Package: "MSR_PKG_ENERGY_STATUS" and DRAM: "MSR_DRAM_ENERGY_STATUS"
are counted on 32 bit ( the MSRs are 64bit wide) and they wrap around every few minutes.

for info check out the attached screenshot of the Intel's doc
or here for Intel's complete doc: http://download.intel.com/products/processor/manual/325384.pdf

user mark the state canceled instead of completed.

so it gets sent again.  This isn't a major problem since the start will
happen when the job ends, but this does make things cleaner.