This corrects logic from commit e5a61746
that could result in use of NULL pointer

It was previously triggered by executing "scontrol reconfig" on a
  front-end system while there was a job in completing state.

The counter is really intended to reflect the count of running or
  suspended jobs rather than running jobs alone. Previous logic
  would report an underflow for the "job_cnt_run" variable if
  1. job submitted
  2. job suspended
  3. scontrol reconfig
  4. job cancelled

No change in logic

Support taking node out of FUTURE state with "scontrol reconfig" command.
Previous logic would keep node in FUTURE state if that was the original
configuration when slurmctld started. If job was running on the node,
it will stay running, but the node make not be visible.

accounting correctly to avoid meaningless errors about overflow.

and a node is older it will stop communicating completely.

And various changes/updates.

This can (hopefully) be used as an example when adding new TRES in the
future.

and call it when the job state is read instead of in the middle of
a reconfig which may be too late as the priority plugin needs the arrays
set up when _sync_nodes_to_comp_job is called in slurmctld/read_config.c

or not.

tracked tres info since we want to keep tabs on everything whether we
track it or not just incase we start to.

changes.

Replace logic of this form:
   if (x) {
     list_destroy(x);
     x = NULL;
  }
with the simpler
FREE_NULL_LIST(x)
bug 1785

Bug 1743

Bug 1743

utilization.

If a job had a reservation, it would try to find the reservation
before the resv_list was populated.

it does not provide any information and make things longer than necessary.

Add a stage 1.1 in the loading of the layouts in order to recover the updated
entities prior to building the relationships among them (stage 2) using the
states saved in Slurm state save location for the layouts to load.

Information concerning the relations among entities provided by the 'Enclosed'
conf pragma are not taken into account for now when reading from layouts state
files. No layout plugins callbacks are called when doing that for now.

Add the ability for a compute node to be allocated to multiple jobs, but
restricted to a single user. Added "--exclusive=user" option to salloc,
sbatch and srun commands. Added "owner" field to node record, visible using
the scontrol and sview commands. Added new partition configuration parameter
"ExclusiveUser=yes|no".  Add "Shared=user" job state information.