If a task in a parallel job fails and it was launched with the
    --kill-on-bad-exit option then terminated the remaining tasks using the
    SIGCONT, SIGTERM and SIGKILL signals rather than just sending SIGKILL.

Sinfo command with support for federated clusters

The job was completing before the test could find that the job was
running. The script was running for 10 seconds and wait_for_fed_job can
back off and check only every 10 seconds.

Can't use the revoked state to determine if the job is pending or not
since an origin job could be revoked if it doesn't have an active job on
itself.

Coverity CID 45347

Coverity CID 45345 and 45346

Coverity CID 45342

Coverity CID 45340

Coverity CID 45341

Avoid comparision between double and int
Coverity CID 45336

Coverity CID 44687

This eliminates comparing a double with an integer
Coverity CID 45337

Coverity CID 44872

Add slurm_load_partitions2() function to route RPC to specific cluster
Add slurm_load_node2() and slurm_load_node_single2() functions to
  route requests to specific cluster in a federation
Modify srun to get node/partition information for each cluster in a
  federation at the same time using separate pthreads
Add sinfo sort by cluster name (--sort V)

Updating after changes to show partition name.

Refactor the functions used to load state information.
  Reservation and BG block information will be local only.

Add --local option
Add %V/%cluster format option to print cluster name

If there were no clusters in the system then the dbd would insert a row
in the database and then on the next time the dbd would start (with no
clusters) it would attempt to insert the row again and fatal. Now it
always makes a query against the database and if there are no clusters
in the system, then it inserts the current db version into the table.

Without this test the macro _entity_update_kv_helper() will use a
  NULL value for oldvalue and abort
Coverity CID 44965

Treat the same as having the --local option and only get information
  from the identified cluster.
If sprio --cluster option is set, then implicitly set --local

Fix the sprio API so that jobs that are on remote federations only
  and in multiple partitions do not remove all but one partition's
  record. Use a hash function to turn the partition name into a
  number and insure that every unique job ID & partition name are
  reported by sprio.

See Coverity CID 56711

If sysconf() fails, it returns -1, which was not being handled
  properly.
  Coverity CID 59941

The sort list function was flawed and there was a bug in the job
priority API used by sprio

Add sprio --local and --sibling options for use in federation of clusters.

Move the function to get job priorities from src/sprio to src/api
  so that we can handle the threading required for federated clusters
  in a common location in the event this logic is used from other
  places in the future (e.g. sview). No fundamental change in logic.
  The logic and definitions were just moved.

Add sprio -p/--partition option to filter jobs by partition name.
Add partition name to job priority factor response message.

Modify backfill logic so that bf_max_job_user, bf_max_job_part and
    bf_max_job_user_part options can all be used independently of each other.