increment ids for the tres_table.

Bug 4553

Turns out auto_increment=# doesn't work in MySQL at the time of writing
but does work correctly in MariaDB >=10.2.4+

See bug for more information.

This reverts commit 12794fb0.

increment ids for the tres_table.

Bug 4553

Turns out auto_increment=# doesn't work in MySQL at the time of writing
but does work correctly in MariaDB >=10.2.4+

See bug for more information.

_run_prog() executes after a fork(), if some thread in the parent
was holding slurm_conf_lock() it would never be released, and the
child will deadlocked.

Already fixed for 17.11 by commit e205eeaf, this backports just
the change for _run_prog().

Bug 4562.

This adds support for the --bb option "access_mode" in addition to
  "access" for better compatability with Cray's DataWarp options.
Related to bug 4528

Remove errant '2' from the macro name.

In 1.10+ they changed the hid_t from an int to a long int which
messes things up as they use the top 32 bits for stuff right off
the bat.  This fixes the scenario by handing the number with a int32_t
instead of an int.

Bug 3795

Since NO_VAL = SLURM_BATCH_SCRIPT, the else statement would only compare
the job_id and not the step_id, thus when a batch step was removed all
the steps from that job would be removed too. Then when attempting to
remove the extern step in the next iteration, it was already removed
and we were incorrectly erroring out.

Bug 4458.

Fix memory leak of MailDomain configuration string when slurmctld daemon
   is reconfigured.
bug 4272 (comment 35)

slurm_load_job() prior to 17.11 returns the error code in errno and not
in rc.  With the addition of 47175901 if a job is removed from memory
before sbatch checks for the job again, sbatch could get in an loop
checking for the job. This only happens if you have a very small
MinJobAge (<10) -- which is not recommended.

Bug 4445

Bug 4444

Bug 4323

Bug 4299

Bug 4299

Bug 4299

bug 4442

Bug 4440

bug 4443

bug 4441

Bug 4306.

to start.

Bug 4434

Bug 4433.

Bug 4404.

Bug 4323.

This now matches the sinfo documentation.

Bug 4306.

Issue could be triggered when updating a partition node(s) with node(s)
that were already in the partition, incorrectly increasing the
node_record->part_cnt (number of associated partitions) and thus
incorrectly extending the array of pointers to partitions associated
with this node, leading to an array with repeated associated
partitions pointers.

Bug 4318.

On CLE 6.0 mungedir is /usr; a 'module unload' call then removes /usr/bin
from PATH which is rather inconvenient.

Bug 4334.

This needs to be an email address, but slurm-dev (now slurm-users)
will drop postings from non-subscribors. Just drop the setting instead.

Mailing list has been renamed. Update links.

Drop Gmane link, as they apparently stopped archiving things
over a year ago, and the relay point has now been dropped from
the slurm-users list.

Drop mentions of emailing slurm-dev from the FAQ. The mailing
list auto-discards anything from non-subscribors.

Memory TRES was getting the pn_min_memroy value when updating the job.
But the TRES memory value is the total memory of the job
(e.g pn_min_memory * cpus || pn_min_memory * nodes).

Bug 4177

Bug 4172

This reverts commit f07514c0.