This issue was addressed differently and the original 1 second
sleep can be restored for easier performance comparison with
Slurm verstion 14.03.

Previously job would only run in first listed partition.

Fix gang scheduling for jobs submitted to multiple partitions.
Previous logic assumed the job's "partition" field contained a
single partition name, that in which the job is running. That
was recently changed in order to support job's being requeued,
which we want to be runable in all of it's valid partitions.

backport of commit 9b4f3634

Previously the --partition option would not work with the new
--priority option for jobs submitted to multiple partitions.

Added squeue -P/--priority option that can be used to display pending jobs
in the same order as used by the Slurm scheduler even if jobs are submitted
to multiple partitions (job is reported once per usable partition).

Modify job array logic to properly support the MaxJobCount
configuration parameter with the new job array data structure.

This part handles the decrement portion of logic.

Rename the function local variable "job_count" in order to avoid
confusion with the global variable by the same name.
No change to logic.

NFS file system delays was causing the test for file existence
to periodically fail. Adding an "ls" call syncs the file system
and fixes the problem.

Check separately for globals file existence and permissions

instead of guessing off the exit_code.

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.