Add ValidateMode configuration parameter to knl_cray.conf for static
    MCDRAM/NUMA configurations.
bug 3736

still think there are steps running.

Bug 4719

# Conflicts:
#	src/slurmctld/controller.c

This should expose O_CLOEXEC on older glibc versions,
addressing build issues on CLE 5.2.

Bug 4843.

There are a few other unguarded uses of this.
Adding _GNU_SOURCE at the top of these files should expose this
macro instead.

This reverts commit 44775add.

MsgType=6500 wasn't being expanded:

"
slurm_persist_conn_open: Something happened with the
receiving/processing of the persistent connection init message to
XXX.XXX.XXX.XXX:6819: Failed to unpack MsgType=6500 message
"

Bug 4924

(slurmdbd was down when slurmctld was started).

Bug 4864

Bug 4864

Set scontrol exit code to 1 if attempting to update a node to
DRAIN or DOWN without specifying a reason.

Bug 4920.

bug 4717

GCC-7 with -Wformat warns about

node_features_knl_cray.c:2869:33: warning: ‘%d’ directive output may be
truncated writing between 1 and 10 bytes into a region of size 8
[-Wformat-truncation=]
     snprintf(buf, sizeof(buf), "%d", i);
                                 ^~
node_features_knl_cray.c:2869:32: note: directive argument in the
range [0, 2147483647]
     snprintf(buf, sizeof(buf), "%d", i);
                                ^~~~
In file included from /usr/include/stdio.h:862:0,
                 from ../../../../slurm/slurm.h:68,
                 from node_features_knl_cray.c:66:
/usr/include/bits/stdio2.h:64:10: note: ‘__builtin___snprintf_chk’
output between 2 and 11 bytes into a destination of size 8
   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        __bos (__s), __fmt, __va_arg_pack ());
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Increasing the buffer to 12 for this.

Bug 4900.

Signed-off-by: Justin Lecher <jlec@gentoo.org>

Add DefCpuPerGpu and DefMemPerGpu to global and per-partition
configuration parameters. Shown in scontrol/sview as "JobDefaults=...".

to find the pointer.

when slurmctld was started) you could loose QOS usage information.

Bug 4865

To be used in a future commit for Bug 4865

no steps or params.pid_format is used.  This also fixes a memory leak.

Bug 4904

the new 'flags' field of slurmdb_job_cond_t. Added new flag
JOBCOND_FLAG_RUNAWAY for listing only runaway jobs.

Bug 4847

Bug 4847

# Conflicts:
#	doc/html/faq.shtml
#	src/plugins/job_submit/lua/job_submit_lua.c

1c92134d

6bc5dc30
6d4518fe

static.

This reverts commit afdd8778.

Turns out MsgAggregation hits a race condition here where the
assoc_mgr_tres_list might not be set up yet.  Reverting this commit
makes everything work as expected.  It was only added in the first
place as convenience.

Otherwise incorrect status could be registered in the database and completed
jobs be seen as pending, running, and so on.

Bug 4847

set to not be shown as runaway.

Bug 4847

Otherwise incorrect status could be registered in the database and completed
jobs be seen as pending, running, and so on.

Bug 4847

Add infrastructure for per-job and per-step TRES parameters: tres-per-job,
    tres-per-node, tres-per-socket, tres-per-task, cpus-per-tres, mem-per-tres,
    tres-bind and tres-freq. These new parameters are not currently used, but
    have been added to the appropriate RPCs.

This does not add the new fields, but just duplicates the v17.11
  logic. The next commit will indentify what changes.

Non-pack jobs were getting their pack_offset set to -1, which resulting
in a bad pack_group value being reported for non-pack steps which were
killed.

We already use an unguarded #define _GNU_SOURCE throughout the code,
so clean these out #ifndef guards out just for consistency.

Looks like a regression accidentally introduced in d8770a66.

Bug 4769.