When more than 1 ping cycle is spawned simultaneously (for instance
REQUEST_PING + REQUEST_NODE_REGISTRATION_STATUS for the selected nodes),
we do not track a separate ping_start time for each cycle. When ping_begin()
is called, the information about the previous ping cycle is lost. Then when
ping_end() is called for the first of the two cycles, we set ping_start=0,
which is incorrectly used to see if the last cycle ran for more than
PING_TIMEOUT seconds (100s), thus incorrectly triggering the:

 error("Node ping apparently hung, many nodes may be DOWN or configured "
       "SlurmdTimeout should be increased");

Bug 3914

Bug 3941.

44e2b1a9 and where the functionality was promptly removed a few days later
in 51076871.  Thanks to Artem Polyakov for pointing out the history :).

 -- Add slurm.conf configuration parameters SlurmctldSyslogDebug and
    SlurmdSyslogDebug to control which messages from the slurmctld and
    slurmd daemons get written to syslog.
 -- Add slurmdbd.conf configuration parameter DebugLevelSyslog to
    control which messages from the slurmdbd daemon get written to syslog.
bug 3933

ee84f5c1.

like slurm_switch_ops_t instead of the new dynamic_plugin_data_t.

Bug 4025

Reported by Coverity, CID 45140 and 45141

pack_job_id was being reported as pack_job_offset

Get rid of any race conditions and call anything that was in
_pre_task_privileged from the parent instead of the child.

NOTE: This should be safe as we don't execute the task until after
_exec_wait_child_wait_for_parent is signaled which happens after all this is
long over.

Bug 3865

Fix regression in commit e5c05549 that would put the stepd pid into the memory cgroup instead of the task's pid.

Beforehand this would put the result of getpid() into the cgroup.  Before
e5c05549 this was done in the child of the fork which would get you
the task's pid, but moving it to run in the parent broke this logic.

What this patch does is adds pid to the input parameters of
task_g_pre_launch_priv making it so we could use the correct pid.

Regression in commit afeca4e2. Bug 4026.

Bug 3953

Pretty much fix the entire purpose of this max_agent_queue.

Bug 3159

Bug 3956

Bug 3967

step wasn't always gathered correctly.

Bug 3531

This removes several define statements with different names in
  various functions

Fix for possible slurmctld abort with use of salloc/sbatch/srun
    --gres-flags=enforce-binding option.
bug 4008

Update from commit b40bd8d3

Clarify --immediate option.

By removing the real locks we can get into a race condition where the prolog
starts and finishes before we get here and then we end up waiting forever.

Making the mutex a static seemed to help in many cases, but didn't
completely close the window.  Changing slurm_cond_wait to
slurm_cond_timedwait fixed the scenario where we would hit the window, but
not degrade performance the original commit provides.

There were also spots where if the job or step didn't exist it wouldn't
signal the conditional also providing a spot this could get stuck not
starting the job.

Fix regression from commit 52ce3ff0

Bug 3977