rights by a secondary group id.

Bug 4439

introduced in commit ea85d123

Bug 4613

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.

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

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

Fix output file containing "%t" (task ID) for heterogeneous job step to
    be based upon global task ID rather than task ID for that component
    of the heterogeneous job step.

Fix for possible memory corruption in srun when running heterogeneous
job steps.
bug 4626

This partially reverts 89bcd975 and aac6bd39

Turns out you can't use a list_for_each and lock something inside the
list_for_each function that does a lock without the write lock.

Bug 4611

This reverts commit ff3e77f4.

This partially reverts 89bcd975 and aac6bd39

Turns out you can't use a list_for_each and lock something inside the
list_for_each function that does a lock without the write lock.

Bug 4611

Fix job array dependency with "aftercorr" option and some task arrays in
    the first job fail. This fix lets all task array elements that can run
    proceed rather than stopping all subsequent task array elements.
Bug 4590

Creating a copy of the actual environment in env->env defines a new pointer,
then next call to setup_env and setenvf doesn't define variables in the global
environment but in this new copy.

Bug 4615

node_feature/knl_cray - Fix memory leak that can occur during normal
    operation. This will happen when an update request for a specific
    node happens.

If CnselectPath and/or SyscfgPath defined in knl_cray.conf file and
  slurmctld reconfigured, the original values of those paraemters
  would be over-written and their memory leaked.

Use FREE_NULL_BUFFER instead, otherwise we could attempt to
free_buffer a second time if we jump to the rwfail label.

bug4491

to preempt other eligible jobs.

Bug 4279

Missing from 390da8cf

Bug 4595

Bug 4127

When --mail-type option isn't requested with ARRAY_TASKS, we need somehow
to summarize the different states each task finished in the array. We've
added a new ARRAY_TASK_REQUEUED flag to the array_flags to indicate that
at least one task was requeued. Also the logic now detects if at least
one task failed and/or if otherwise all finished successfully.

The patch also removes the RunTime from the the e-mail when summarizing
whole array, since it doesn't make sense to specify just the RunTime
of one of the tasks for this case.

Patch also fixes when ARRAY_TASKS is specified, previously the mail
notification for the master job task record included a range of
ExitCodes for all the tasks. Since this option is not for summarizing,
the patch makes it so only the range is shown when the option isn't
specified.

Bug 4539.

Scheduling fix for changing node features without any NodeFeatures plugins.
Bug 4577

Avoid setting node in COMPLETING state indefinitely if the job initiating
the node reboot is cancelled while the reboot in in progress. Bug
introduced in commit 7d246784

Bug 4536

Bug 4448

Logic was backwards before.

Bug 4459.