Bug 1550

their own jobs.

Bug 1469

A non-administrator change to job priority will not be persistent except
for holding the job. User's wanting to change a job priority on a persistent
basis should reset it's "nice" value.
Without this change a user might lower a job's priority, but Slurm will
not lower it more based upon fair-share changes.

Bug 1469
Return values from void functions are unknown and were causing
list_for_each to short ciruit processing of the job list.

This is a correction to patch 5a9277b1

Fix for misleading job submit failure errors sent to users. Previous error
could indicate why specific nodes could not be used (e.g. too small memory)
when other nodes could be used, but were not for another reason.
bug 1537

Correct the job array specification parser to accept brackets in job array
expression (e.g. "123_[4,7-9]").
This patch superseeds patch 8d811201
bug 1552

The logic fails if there are commas in the brackets:
slurmctld: job_str_signal: 3 invalid job id 1593_[2,5-6]
Updated patch in next commit
bug 1552

This just releases the requeue_exit and requeue_exit_hold arrays
when the slurmctld shuts down so we can more easily identify any
real leaks.

This reverts commit 5bd97a2c.

RequeueExit and RequeueExitHold configuration parameters modified to accept
numeric ranges. For example "RequeueExit=1,2,3,4" and "RequeueExit=1-4" are
equivalent.
bug 1549

If SchedulerParameters value of bf_min_age_reserve is configured, then
a newly submitted job can start immediately even if there is a higher
priority non-runnable job which has been waiting for less time than
bf_min_age_reserve.

Start job allocation using lowest numbered sockets for block task
distribution for consistency with cyclic distribution.
bug 1540

Continuation of f34c6bbf

block is set up to it's original state.

Bug 1533

Logic was bad in last commit

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

If a job is submitted with the option --mem=0, then once the job
is allocated resources, reset that value to the amount of memory
on the allocated node with the smallest amount of memory. This is
probably the best option for right now. The downside is that if
the job is requeued, its memory size will no longer be the total
memory on all nodes if the cluster is heterogeneous. On the upside,
some memory data is available for accounting purposes.
bug 1526

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