Change how a node's allocated CPU count is calculated to avoid double
    counting CPUs allocated to multiple jobs at the same time.
    Previous logic would sum the maximum number of CPUs allocated by each
    partition for any time slice, which could double count CPUs allocated
    to multiple jobs. New logic ORs bitmap of allocated CPUs for every
    partition and time slice, then counts the total for a given node.
    This avoids double counting CPUs allocated to multiple jobs, but
    does not remove from the count CPUs which have been allocated to
    jobs which might be suspended by the gang scheduler (either for
    time slicing or preemption).

Update NEWS as well.

The uid is used as part of the hash function, must remove old reference
and recalculate if it may change, otherwise _delete_assoc_hash
will not find it again when the association is removed, causing
slurmctld to segfault.

Bug 2560.

Add --gres-flags=enforce-binding option to salloc, sbatch and srun commands.
    If set, the only CPUs available to the job will be those bound to the
    selected GRES (i.e. the CPUs identifed in the gres.conf file will be
    strictly enforced rather than advisory).
bug 1725

Previous gang scheduling logic maintained information about resources
  originally allocated to the job and made scheduling decisions on
  that basis.
bug 2494

This will improve ability to diagnose problems if the srun is
killed by a signal.

Update gang scheduling table when job manually suspended or resumed. Prior
    logic could mess up job suspend/resume sequencing.
bug 2494

time.

https://bugs.schedmd.com/show_bug.cgi?id=2547

The code just wasn't fully baked before and was probably written before
a lot of the other supporting code was done i.e
assoc_mgr_set_assoc|qos_tres_cnt were done specifically for this kind of
thing.  Many of the usage structures weren't realloced either as well as
the tres_cnt local to each qos and assoc wasn't updated.  So all in all
pretty bad code - bad Danny.  This makes sure all this sets up and no
memory corruption happens.

Generate burst buffer use completion email immediately afer teardown
    completes rather than at job purge time (likely minutes later).
bug 2539

Change burst buffer use completion message from
    "SLURM Job_id=1360353 Name=tmp Staged Out, StageOut time 00:01:47" to
    "SLURM Job_id=1360353 Name=tmp StageOut/Teardown time 00:01:47"

This is being fixed in shortly be creating a separate library for
bcast functionaltiy

Bug 2396

Bug 2548. No functional change, documentation only.

Conflicts:
	src/plugins/burst_buffer/generic/burst_buffer_generic.c

Otherwise "not found" value of -1 for tres_pos would cause
out-of-bounds memory access.

Conflicts:
	src/plugins/burst_buffer/cray/burst_buffer_cray.c

Bug 2543.

Fix bad cast in 3a604563, and update pct to 64-bits to prevent
truncation of intermediate value (pct * 100).

resolve NoInAddrAny when doing a strstr.  Continuation of commit 775c46de.

on only one port like TopologyParam=NoInAddrAny does for everything else.

There's no /proc on *BSD, and BSD handles OOM in a completely different way.

Dividing a negative int by a positive can have unexpected behavior -
C99 requires "truncation towards zero". This was to an incorrect output
of:

sbcast: File compressed from 104857600 to 104889678 (40 percent) in 2160081 usec

when testing with a file of random data. This is actually negative 0
(point something that was truncated) compression, not "40".

Conflicts:
	NEWS
	src/smap/Makefile.am