Fix bug that can permit someone to kill job array belonging to another user.

Fix support for --mem=0 (all memory of a node) with select/cons_res plugin.
Previously the job would not have it's memory constrained, but it would not
make that memory unavailable to other jobs either.
bug 1526

This was previously added to v14.11

Added new SchedulerParameters value of bf_min_age_reserve. The backfill
scheduler will not reserve resources for pending jobs until they have
been pending for at least the specified number of seconds. This can be
valuable if jobs lack time limits or all time limits have the same value.

Increase maximum MaxArraySize configuration parameter value from 1,000,001
to 4,000,001.
bug 1535

Added LaunchParameters configuration parameter. Have srun command test
locally for the executable file if LaunchParameters=test_exec or the
environment variable SLURM_TEST_EXEC is set. Without this an invalid
command will generate one error message per task launched.

Cray - Fix for launching batch step within an existing job allocation.
bug 1509

Partially revert commit 8d91ae22
The bug was introduced in version 14.11.0-pre4.
bug 1504

This is for bug 1514

before.

Bug 1507

message comes in

Bug 1501

Bug 1501

cluster(s) requested.

Bug 1492

For job running under a debugger, if the exec of the task fails, then
cancel its I/O and abort immediately rather than waiting 60 seconds for
I/O timeout.

The option has not been functional or documented since Slurm version 2.0.

This controls how long a requeued job must wait before it can
restart, and 20 minutes is too long in most cases. Administrators
can alter this configuration parameter if needed in case of slow
Prolog or the like.

Use this to specify the lifetime of a job step credential.

Bug 1476

Set the delay time for job requeue to the job credential lifetime (1200
second by default). This insures that prolog runs on every node when a
job is requeued. (This change will slow down launch of re-queued jobs).
Without this change, if a job is restated within 1200 seconds, the nodes
previously used would not run the prolog again, since the job ID is
still seen as active (from the previous execution). It is also advisable
to set the value of DEFAULT_EXPIRATION_WINDOW in src/common/slurm_cred.c
to the lowest value reasonable. We need to add a new configuration parameter
so this is easly changed in the future.

Display job's estimated NodeCount based off of partition's configured resources rather than the whole system's.

Bug 1478

Previously, there was no binding of tasks to the appropriate NUMA.
Based upon work by Josko Plazonic <plazonic@princeton.edu>.

Mail notifications on job BEGIN, END and FAIL now apply to a job array as a
whole rather than generating individual email messages for each task in the
job array.

Bug 1469

The /root/.my.cnf would typically contain the login credentials for
root.  If those are needed for Slurm, then it should be checking
that directory.

(In reply to Nina Suvanphim from comment #0)
...
> const char *default_conf_paths[] = {
> "/root/.my.cnf", <<<<<<<<<<<<<<<<<------- add this line
> "/etc/my.cnf", "/etc/opt/cray/MySQL/my.cnf",
> "/etc/mysql/my.cnf", NULL };

I'll also note that typically the $HOME/.my.cnf file would be
checked last rather than first.

don't support strong_alias