occur naturally if a srun, scontrol, scancel, sinfo, or squeue command is
killed by the user with a communication to slurmctld in progress. This
seems to occur fairly regularly as part of batch job termination.

send/receive, function (poll, timeout, send, recv, etc), and the error message
are all reported.

resources to satisfy the request).

This prevents an orphan job if srun dies after sending the request
or the network fails or the authenticaion mechanism fails.

logging the event and returning SLURM_SUCCESS.

It was picking zero nodes and failing.

   problem when debugging remote tasks. (and error should have only
   printed once anyway)

   not SIGXCPU on reaching timelimit.

It was formerly just killing the job step processes.

to match that of a job's run time (TIME).

hand if race condition starting all daemons).

 o Export SLURM_NODELIST environment var in all cases

 o Changed correspondingly calls to above
 o Removed unnecessary envc member of job structure, along with references
   to said member

    is through with them.
 o added new function unsetenvp() to support above

the old_job_allocation response so as to conform with job step's specification.
For example, remove nodes that are excluded (-x), set the node count to
that requested (-N, eliminate nodes as required), etc. This requires
modifying the node list including the slurm_addr, and cpu_count arrays.

Add new logic to prevent some node state transitions via update_node RPC
(e.g. IDLE to ALLOCATED).

By default, logging is to syslog. Expanded usage description to be more
complete.

without duplicates. For example, we want to convert a users request for
nodes "lx1,lx2,lx1,lx3" to "lx[1-3]".

entry counting function. As a job is completing the bitmap gets cleared
as nodes complete, resulting in incorrect values.

job is scheduled.

required by a pending job. NOTE: On heterogeneous systems or if the
requested number of nodes is a range then the actual number of nodes
allocated may differ from the value displayed.