Just in case reboot_program doesn't actually turn this node off
for some reason, at least stopping slurmd explicitly will keep
the node offline until someone intervenes.

Bug 5019.

Add configuration paramerers SlurmctldAddr for use with virtual IP to manage
    backup slurmctld daemons.
bug 4768

Add configuration paramerers SlurmctldPrimaryOnProg and
    SlurmctldPrimaryOffProg, which define programs to execute when a slurmctld
    daemon becomes the primary server or goes from primary to backup mode.
bug 4768

When any of these --exclusive modes couldn't be satisfied, Slurm was
returning an incorrect ESLURM_NODE_NOT_AVAIL, having as a consequence
scheduling problems as described in the bug. The fix makes it so the
error code is properly set to ESLURM_NODES_BUSY, fixing also the
scheduling problems and working over the correct share_node_bitmap.

Continuation of commits from bug 4932:
e2a14b8d
fc4e5ac9

Bug 5047.

Fix an issue in the bit manipulation log introduced in commit 892ffa89.

Bug 4997.

Replace select_p_select_jobinfo_sprint() with the same NO-OP
that the other plugins (except alps and bluegene) have implemented.

Bug 5077.

Time limit was incorrectly changed when swapping qos. Now we check
qos/assoc/partition all together and deny the chang if not consistent.
Fixed how we check coordinator permissions. Rearranged the function to update
QOS before updating partition in order to enforce AllowQOS and DenyQOS options.
One memory leak and some comments fixed too.

Bug 4685

1. Identifies nodes which are unavailable to a specific job,
adding a call to filter_by_node_owner() in select_nodes()
 where the node list is generated.
2. Removes the "unavail_node_str" argument to select_nodes()
as it is no longer useful. This string originally was originally
generated once at the start of the job scheduling logic for all jobs,
but since each job can have a different set of
 unavailable nodes (dedicated to user, group, etc.)
so the same string for all jobs can be misleading.

Bug 4932.

See commit 0dabf4e7.
Bug 4932.

regression from ef1f3e73.
Bug 4885.

If scaling_available_frequencies file is not available, then derive
values from scaling_min_freq and scaling_max_freq values. If
cpuinfo_cur_freq file is not available then try to use scaling_cur_freq.

bug 4910

over any other nodes.

Bug 4968

allocated time than 100% (Flex reservations).

Bug 4968

Bug 4968

bug 4968

In configurator.html web pages change default configuration from
    task/none to task/affinity plugin and from select/linear plugin to
    select/cons_res plus CR_Core.

Only one of a set of OpenMP processes will be marked as dumping
core, but terminating any of them will interrupt this and lead to
a partial core file being written.

Test all processes in the task, and only signal them if none are
writing out a core file. Otherwise wait and try again later.

Bug 4624.

Bug 4952.

Bug 5011.

If an update for a job that is being requeued[hold] happens, we don't want
to modify the start_time of the old record. Pending + Completing is
equivalent to Requeue.

Bug 4855.

Bug 3318

Missed from 500e23b5

Bug 4988

job_ptr was still being referenced after releasing the read locks. Also
prolog_running_decr() needs to have a job write lock and a fed read
lock.

Bug 4947

Avoids confusion with the %u header of USER.

Bug 4948.

Bug 4990.

While restarting slurmctld with -R flag, features were emptied.
This patch just does nothing when recover=2 (-R) which means active and
available features are preserved from the state files. Needed for
backup slurmctld controller.

Bug 4927

Bug 4882

If block_map_size is zero (as seen on FreeBSD when not using HWLOC),
xmalloc(0) will return NULL. Writing to str[0] then is invalid.

Bug 4845.

Bug 4971

-X doesn't show cumulative statistics for each job but statistics relevant to
the job allocation itself.

Bug 4967

It fixes a scontrol segfault when updating a reservation with empty users or
accounts and the parameters were specified more than once.

Bug 4945

Bug 4778

Bug 4949