Support GRES types that include numbers (e.g. "--gres=gpu:123g:2").
Also change number suffix processing to use common function
See commit 396e82a167
bug 6345

This is useful for testing and debugging.

Bug 6321

As pthread_rwlock_t is a struct, we cannot use this syntax
to initialize all elements of the array to the same value
as we would if these were any basic type.

Instead, move the initialization to a dedicated loop to ensure
all locks are initialized correctly.

This does not seem to have caused any issues on Linux platforms,
but macOS at least does notice this mistake.

Bug 6319.

Add logic in read_config.c to handle old config option name.

Bug 5916.

Added a new DebugFlag=accrue to show debug messages related to accrue time
count or other related stuff.

Bug 6096

Enabling this alters the scheduling sorting algorithm so that hetjob
components belonging to the same hetjob are attempted to be scheduled
consecutively (not interleaved with other jobs or hetjob components).

Bug 5579.

AccrueTime limits.

Bug 6002


Co-authored-by: Felip Moll <felip.moll@schedmd.com>

Regression introduced in ccafaf7b.

Replace the (was always set to true) check_current_dir argument to
search_path() with check_cwd_last boolean to indicate if cwd should be
evaluated first (needed by sbatch) or last (salloc/srun).

Bug 6271.

Kill running/pending job is allocated GRES and that GRES has a "File"
    configuration, and the GRES count changes.
Also generally better handle changes in GRES count (avoid some bugs
    in GRES data structures).

bug 6169

This reverts commit 34633d9b.

Bug 6169

Added extra check of name in setenvf() to ensure name is not an empty
string.

bug 6169

Bug 6283

SizesByAccount and SizesByAccountAndWckey now defaults to display the
root account totals, or the exact requested Account=. To query like the old
behavior a new option 'AcctAsParent' has been added which will still shown
the subaccounts of the requested accounts in Account=.

Bug5793

Bug 6289

Introduced in d9b9eb23

Bug 6292

Bug 5441

Co-authored-by: Felip Moll <felip.moll@schedmd.com>
Co-authored-by: Danny Auble <da@schedmd.com>

Bug 5441

Bug 5971

from a node.

Bug 5971

Bug 6229

Bug 6239

Bug 6229

bug 6197

Bug 6239

backport of 03ada72e

Bug 5682

Bug 5682 and 4584

Backport of ba07a6e09b6071

other than knl.

Bug 5603

Bug 5603

This patch also simplifies the code using bit_cnt instead of
_bitstr_bits().  This isn't really necessary, but does look cleaner.

Bug 6216

It was using the local cluster, sending the query to the wrong table

Bug 6159

Bug 6237

if OverTimeLimit is Unlimited.

Bug 6093

New X11 forwarding code will only support forwarding back to
salloc or an allocating srun command.

Using this option within sbatch was always hit-or-miss. If the
user submitting was disconnected from the alloc host for any
reason their xauth credentials would likely fail even if they
managed to get assigned the same local TCP port for forwarding.

Bug 3647.

In some systems there can be multiple user accounts for uid 0, therefore
the check for literal user name "root" might be insufficient.

Bug 6184

This pam module is tailored towards running in the context of remote ssh
logins. When running in a different context like a local sudo call then
the module could be influenced by e.g. passing environment variables
like SLURM_CONF.

By limiting the module to only perform its actions when running in the
sshd context by default this situation can be avoided. An additional pam
module argument service=<service> allows an Administrator to control
this behavior, if different behavior is explicitly desired.

Bug 6184

Only print a warning for 18.08. If a user has SLURM_MEM_PER_CPU or
SLURM_MEM_PER_NODE environment variables set for some reason this
situation could be happening by accident, and we don't want to prevent
the srun command from launching steps at this point.

Bug 6058.