Bug 4548

The original logic was preventing a second step from starting due
  to propagating the job's memory limit, which caused the test to
  fail.

Bug 4634

job container where if the step was canceled would also cancel the stepd
erroneously.

Bug 4634

one already exists owned by a different user will be logged and the job
held.

Bug 4614

Bug 4681

Bug 4683

from when last started.

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

if LaunchParameter test_exec is set.

Bug 4439

rights by a secondary group id.

Bug 4439

Bug 4439

bug 3536

Bug 4674

introduced in commit ea85d123

Bug 4613

CID 182336

Coverity CID 182335

Commit 818a09e8 introduced a new state JOB_OOM and a new state reason
FAIL_OOM (OutOfMemory). The problem was that it based the decision upon
the value of the different memory.[*].failcnt being > 0.

That lead to "false positives" situations when the usage hit the limit
but the Kernel was able to reclaim pages and the process managed to finish
successfully. When this happens there might not necessary be OOM_KILL
events happening.

This patch makes it so the JOB_OOM state is set based upon OOM_KILL events
detected instead of usage hitting the limit. The usage hit will still
be logged as an info() message, and further work will be needed in the
master branch to better discern both type of events, maybe changing
the API and getting rid of the current SIG_OOM and a potential new
SIG_OOM_KILL.

OOM_KILL event is detected using the eventfd notification mechanism
on the cgroup v1 control/event files:
https://www.kernel.org/doc/Documentation/cgroup-v1/memory.txt

If we plan to support cgroup v2, we should monitor 'memory.events' file
modified events. That would mean that any of the available entries changed
its value upon notification.
Entries include: low, high, max, oom, oom_kill:
https://www.kernel.org/doc/Documentation/cgroup-v2.txt
https://patchwork.kernel.org/patch/9737381
but since this is a fairly recent change many sites might be running
kernels still not supporting this feature.

Bug 3820.

Bug 4656.

This reverts commit d3141dc9.

Bug 4655

Turns out there are many ways to get this information directly from
the slurmstepd.  As you can already get this information from ps we
decided to just revert back to the old non-authenticated way of doing
things.

If we do need this in the future we need to patch the stepd as well as
the slurmd here in all the RPC's that try to grab this.

A user could easily run scontrol (or their own home baked thing)
on the node which will give them a direct contact with the slurmstepd.

This reverts commit c4fb9bc3.

This reverts commit d3141dc9.

Bug 4655

Turns out there are many ways to get this information directly from
the slurmstepd.  As you can already get this information from ps we
decided to just revert back to the old non-authenticated way of doing
things.

If we do need this in the future we need to patch the stepd as well as
the slurmd here in all the RPC's that try to grab this.

A user could easily run scontrol (or their own home baked thing)
on the node which will give them a direct contact with the slurmstepd.

Bug 4656

Bug 4619.

switch count.

Bug 4381

Bug 4620

Bug 4620

find jobs that ran on specific nodes.

Bug 4602

needed if you are ever working with multi-dimensional systems.

Bug 4602

This isn't a real problem, but older compilers will complain about it.
Newer compilers know in order to get into the place it could be used
'have_count' would have to be set.  If that is set then feature_list
would also be set.

itself.

Bug 4638