bug 1884

No changes in logic

Don't generate an error when a batch job is submitted that must wait
  for stage-in before starting.

Bug 2886

Add new SchedulerParameters option of bb_array_stage_cnt=# to indicate
    how many pending tasks of a job array should be made available for burst
    buffer resource allocation.
bug 1884

Conflicts:
	src/sstat/options.c

Was incorrectly translating request to job.extern if part of a
comma-separate list.

Bug 2890.

bug 2858

bug 2858

(regression in 16.05.2).

related commit 5d3e5e1e

Bug 2612 and 2886

of the output.

'-' without a '\' in front of it.

Defaults to true, if set to false will not set kmem cgroup
limit. Bug 2748.

Document limitations in burst buffer use by the salloc command (possible
    access problems from a login node).
bug 2883

task/cgroup plugin is configured with ConstrainRAMSpace=yes, then set soft
    memory limit to allocated memory limit (previously no soft limit was set).
bug 2679

of 0.

This might be the cause of run away jobs.  I couldn't see how an end_time
could be 0, but if it was it would just exit and never set time_end to
anything.  At least if it happens now we can have an idea that it is
possible and we will have an idea this is the place it happens.

This will keep from referencing the task array that might not be set up
correctly in src/common/plugstack.c _spank_handle_init().

Prevent possible incorrect counting of GRES of a given type if a node has
    the multiple "types" of a given GRES "name", which could over-subscribe
    GRES of a given type.
bug 2836

The wrong variable was being used in gres.c to print a message of
this sort:
error: gres/gpu: job 7135 dealloc node ### type ### gres count underflow (# #)
The first number in the parenthesis was based upon the wrong index and it's
contents garbage

cleaning up on a restart.

sleep is killed.

Add port number to the log message and support both IP V4 and V6