Prevent slurmdbd error if cluster added or removed while rollup in progress.
Removing a cluster can cause slurmdbd to abort. Adding a cluster can cause
the slurmdbd rollup to hang.

When allocating resources with resolution of sockets, charge the job for a
CPUs on allocated sockets rather than just the CPUs on used cores.

bug 1595

The error was being triggered by logic to collect accounting
information starting and not being completed when testing to
start a node ping RPC. In other words, the logic wasn't testing
for the completion of one RPC against the start of that same
RPC, but against the start of a different RPC. This change
moves all of the timeout logic into the ping_nodes.c module
where we can make sure that the timing of different RPCs do
not get confused with each other.
bug 1190

This is a correction to commit 1eb32d90
so the select/cray plugin can be built on non-Cray system (for testing).
bug 1587

slurmd was logging:
"Error reading step 2031886.0 memory limits" (with various job/step IDs)
because it was treating SLURM_SUCCESS as an error rather than SLURM_ERROR
bug 1589

Add logging of premature EOF

Disable changes to GRES count while jobs are running on the node.
Previous logic could clear GRES count data and generate counter
underflow then when attemtping to deallocate the job's resources
(including future job terminations when computing when and where
pending jobs will start as part of backfill scheduling logic).
bug 1589

if many steps/jobs finish at once.

bug 1589

bug 1570

A function in sshare changed, which broke several tests.
The commit that broke the tests is 5dacc0fc

Bug 1587

Only lowercase usernames are supported.

switch/cray: If CR_PACK_NODES is configured, then set the environment
    variable "PMI_CRAY_NO_SMP_ENV=1"
bug 1585

gating rpcs.

Signed-off-by: Danny Auble <da@schedmd.com>

added back into the system.

Bug 1578

Bug 1550