Was overwritting data off of buffer passed as argument.

 o Use hostname instead of ip addr string in MPIR_proctable to allow
   TotalView bulk launch capability.
 o Add --jobid option to srun

ranged string rather than one message per node (too verbose).

node begins to respond again.

lowest active job priority (for working down as new jobs are
initiated). This bug only applies when slurmctld restarts and
there are jobs in system hold state (priority 1).

This is a problem on PVC, where nodes are regularly DRAINED.

   srun erroneously expected replies from these hosts (gnats:291)

scalability. An arbitrary number of requests may be queued and they
are processed one per second until the queue is empty or pending
requests were last attempted recently (configuration parameters set
to 60 seconds as a minimum retry interval).

These jobs are reported by slurmd on node registration. They are logged
but otherwise ignored by slurmctld. Several changes to slurmd logging
messaged to report job id and step id using %u format rather than %d
format (which shows no-allocate job id values as negative numbers).

and --nodes options.

--relative option is lower than the node count specified. The --relative
option takes precedence.

that reach the slurm inactivity time limit.

control (it needs to complete all pending RPCs and save state before
the primary reads state and takes over).

responsibilities (backup was routinely reading at startup).

server to shutdown request.

SIGPWR, and SIGLOST.

and when returned to service went improperly back into state DRAINING
(job counter was inconsistent).

transition to DRAINED state.

data will not be used and the process is too slow anyway.

EPILOG_COMPLETE_MESSAGE. At this time the job is COMPLETED and all
associated nodes available.

   on nodes relative to the current allocation.
 o srun no longer sends SIGKILL to job if one task is killed except
   if --no-allocate is used. (the job will otherwise be killed by
   the controller anyway)