and/or job step(s) will have their resources de-allocated and be killed.
A resource allocation will not be release unless no job steps are active
for at least InactiveLimit seconds. DPCS jobs will be subject to this
forced de-allocation if they remain inactive for an extended period of
time, which can get SLURM and DPCS back in sync if DPCS does a cold-start.

were starting multiple jobs simultaneously and slurmd was not able
to respond to all of the requests without generating a message timeout.
(gnats:319)

report an error message.

avoid highly fragmented resource allocations.
Add list of excluded nodes to job info dumpped and reported.
Fix how mis-matched RPC version number are handled. Let error code get
back to the API function.
Dump job state information upon each job's termination via plugin.
Re-issue incomplete write requests in job/partition state save.
Make slurmctld continue proper operation without any default partition
(gnats:317).
Add command/RPC to delete a partition.
Retry socket connection for slurmd/io.c as needed (gnats:253).

and quitting.

to a text file specified in the configure file.

effort of keeping here as there are production version in place.

strtol, which was losing precision.

from slurm_open_stream (which is only called by slurmd/io.c to connect
stdin/out/err).
(gnats:253)

   if have PR_SET_DUMPABLE

is zero.

    jobid and not stepid.)

   not correct.

 o replace calls of pthread_kill() to IO thread with eio_handle_signal()
 o Try to avoid having obj->ops == 0x0

   a side effect.