Since this happens inside a the user process, this can inadvertently
cause the user's job to die by running out of file descriptors.

Bug 7814.

Co-authored-by: William Arndt <warndt@lbl.gov>

Bug 7499

Regression introduced in fb26b706.

Bug 7675

Docs - note that #SBATCH directives stop processing after the first non-comment non-whitespace line.

Bug 7763.

Now the signaling of the batch step and the handeling of the flags is totally
handled in _kill_all_active_steps() in slurmd, and _handle_signal_container()
in stepd to ensure that:
- if KILL_JOB_BATCH then only batch container is signaled
- if KILL_FULL_JOB then batch script and its children are also signaled
- if both of the above then only the batch script and its children are signaled

We do not relay anymore on proctrack_g_signal() to handle the batch step
signaling anymore, therefore it works the same for all proctrack plugins.

This commit also includes minor related fixes in other code handling such
signaling flags, and documentation improvement.

Bug 7282

Bug 7789

gres_device2 should always be defined since device_list is a subset of
gres_devices.

CID 204099

Contiunation of 1cd43fce



Signed-off-by: Michael Hinton <hinton@schedmd.com>

Bug 7630

Continuation of d3df44ca

Bug 7778

Signed-off-by: Tim Wickberg <tim@schedmd.com>

Bug 7697

1cd43fce

Bug 7630

The problem was that MPS and GPU plugins each have separate device
file records that point to the same file (duplicate device files are
normally rejected in gres.conf, so this is a special case). So when a
comprehensive GRES device list was assembled from each plugin in
gres_plugin_get_allocated_devices(), these files were being
double-counted, causing the issue.

The solution is to make this comprehensive GRES list unique by
omitting records with duplicate file paths.

Bug 7630

archive dump and archive load are two complementary options with
different arguments for each.

Bug 7279

Bug 7556

Bug 7727

This was missed in commit 6ac4ce84.

Bug 7754

Using numbers is still supported, however, may be very misleading.
We shouldn't use it in examples.

Bug 7751

Bug 7723

An incorrect logic with the variables holding available cores in the
gres_plugin_job_core_filter3() function lead to a potential infinite
"while (avail_cores_tot > req_cores)" loop, leaving slurmctld unresponsive.

Bug 7685.

Bug 7719

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

Regression caused by 72736af2.

Bug 7708.

FastSchedule will be removed in 20.02.
FastSchedule=2 functionality has been moved to
SlurmdParameters=config_overrides.

Bug 7496.


Signed-off-by: Tim Wickberg <tim@schedmd.com>

Bug 7664

Bug 7699

Continuation of 64876087

Bug 7698

Bug 4781

Otherwise, there could be time frames where printed schednodes
information could be obsolete.

Bug 7676.

exclusively to that job.

Bug 7510

use correct start_time for TIME_FLOAT resevation
in _job_overlap()

Bug 7458

Bug 7458