Revert call to getaddrinfo, restoring gethostbyaddr (introduced in Slurm
    16.05.0pre1) which was failing on some systems. Specifically test7.2
    was failing on some systems with getaddrinfo() returning an error of
    "System error: Resource temporarily unavailable". Partial reversion
    of commit 89621f65

Since the function is inlined the single definition let GCC build everything
properly, but debug builds (which disable inline) resulted in:
slurmstepd: [465.0]: symbol lookup error:
(trimmed path)/task_cgroup.so: undefined symbol: val_to_char
when running srun --cpu_bind=v.

task/affinity had this definition already, task/cgroup didn't.

Kernel option cgroup_enable=memory is likely what you want to fix,
at least Debian and Ubuntu ship with it disabled.

Nothing checks their return code, and it was always success.

While here do some style cleanup. No change in logic.

Change logging from "info()" to "fprintf(stderr, ...)" since this library is called from outside of SLurm proper and will fail in debug mode otherwise.

Reported by valgrind running test7.2, but shouldn't cause any real problem

was also given.

Split partition's "Priority" field into "PriorityTier" (used to order
    partitions for scheduling and preemption) plus "PriorityJobFactor" (used by
    priority/multifactor plugin in calculating job priority, which is used to
    order jobs within a partition for scheduling).
bug 2479

a partition.

This also reverts most of commit fa331e30 as well as commit bd9fa830
which would try to set the pn_min_cpus every time a job was updated.
If a job didn't request node counts then they were hosed.

This commit takes away the magic which was screwing things up.  Now the
person gets what they asked for without magic changing things.

Bug 2302
Bug 2742
Bug 2478

erroneously.

Conflicts:
	src/plugins/select/cray/select_cray.c

Failure has never been observed, but initialize the used variable
  before calling the function so we don't re-use old data if the
  function returns an error.

Rename an improperly named variable in the logic scontrol uses to
  print node information ("total_used" was really "idle_cpus"), so
  the logic looks the same as that used in sinfo to determine node
  state.

Include warning for Cray simulation as reminder for developers to
change code as needed.

This whole process could probably be done better by keeping track of
old values and new values and only calling one function instead of a
pre and post function, but that can probably wait for future generations
of the code as it works now and is probably adequate for the time being.

Bug 2352

e696d308

If a job was requeued while some prolog was running (e.g. waiting
  for node boot, burst buffer, PrologSlurmctld, etc.) then wait
  until that completes before considering starting the job again.

No functional change, although confine to master to limit any
chance of bad interaction with pre-existing plugins.