signal 1.

That should be more robust in this case

Modify crypto/munge plugin to use socket and timeout specified in AuthInfo.

done for normal steps.

Modify AuthInfo configuration parameter to accept credential lifetime
and socket path options. Previously it accepted a socket path only.

of acting like it is a signal and exitcode.

signal only the steps and unless, in the case, of a batch job B is
specified in which case signal only the batch script.

previous it was always -2.

Add node state string suffix of "$" to identify nodes in maintenance
reservation or scheduled for reboot. This applies to scontrol, sinfo,
and sview commands.
Enable scontrol to clear a nodes's scheduled reboot by setting its state
to "RESUME".

Conflicts:
	src/common/slurm_protocol_defs.c

Apply BatchStartTimeout configuration to task launch and avoid aborting
srun commands due to long running Prolog scripts.
bug 978

Provide better description of the slurm.conf configuration parameter
BatchStartTimeout.
bug 979

Disable a partition test if JobSubmitPlugins=all_partitions

When nodes scheduled for reboot, set state to DOWN rather than FUTURE so
they are still visible to sinfo. State set to IDLE after reboot completes.
bug 1007

Srun executable names beginning with "." will be resolved based upon the
working directory and path on the compute node rather than the submit node.

suggest parentheses around assignment used as truth value.

The code tries to load libslurm.so even if precedent dlopen calls
succeeded. The code is structured so that we have to "return;" as
soon as a dlopen succeeds.

This corrects logic introduced yesterday in commit
6f89dc9d which introduced a double
free of step records, at least on job requeue.
bug 1012

Describe restrictions on specific job and step record purging functions
with respect to "cleaning" flag used for Node Health Check on Cray systems.

Always call select_g_step_finish() when terminating a job step,
even if the job is also being terminated. This is needed for Cray
systems.
bug 1012

When a job is requeued, call deallocate_nodes() with a job state
if COMPLETING. Previously it was called with a state of JOB_REQUEUE,
which could be problematic for step complete function calls (which
I am working on fixing now).

Remove some duplicate code. No change in functionality.

When a job record is purged, simply purge the step list rather than possibly invoking a node health check on Cray systems.

No checking or other operations are performed on this list, just a purge.

If an attempt is made to submit a job explicitly using a job ID that already exists, then do not try to purge and re-use it, but return an error. The slow clean-up of job steps on Cray systems due to node health check makes me wary of preserving the existing code. Returning an error seems a safer option.

Call delete_step_records() before clearing the job's JOB_COMPLETING
state flag. This would make a difference in the case of jobs automatically
requeued based upon their exit code, but probably not in other cases.
Also in the select plugins, check not only for a job state of JOB_COMPLETING,
but also FINISHED states. In either case, we are not in a position to
gracefully clean up the step.