decreases and total is less than in use.

mail messages for job array events print now use the job ID using the
format "#_# (#)" rather than just the internal job ID.

it is already running.

job is JOB_COMPLETING or already pending.

last epilog completes, either slurmd epilog or slurmctld epilog,
whichever comes last.

don't clear the dependency if the job is completing.

(Also remove extra pending check, no reason to check it twice ;))

If the backup slurmctld assumes primary status, then do NOT purge any
job state files (batch script and environment files) but if any attempt
is made to re-use them consider this a fatal error. It may indicate that
multiple primary slurmctld daemons are active (e.g. both backup and primary
are functioning as primary and there is a split brain problem).

Test time when job_state file was written to detect multiple primary
slurmctld daemons (e.g. both backup and primary are functioning as
primary and there is a split brain problem).

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

when specified escaped.

Attempt to create duplicate event trigger now generates ESLURM_TRIGGER_DUP
("Duplicate event trigger").

Modify strigger to accept arguments to the program to execute when an
event trigger occurs.

Added strigger option of -N, --noheader to not print the header when
displaying a list of triggers.

batch jobs have cpus_per_task set to zero, which resulted in an
error of "task/cgroup: task[0] unable to set taskset '0x0'"

requeue, requeuehold and release operations.

Do not purge the script and environment files for completed jobs on
slurmctld reconfiguration or restart (they might be later requeued).
Purge the files only when the job record is purged.
bug 834

If a job --mem-per-cpu limit exceeds the partition or system limit, then
scale the job's memory limit and CPUs per task to satisfy the limit.
bug 848

not finished yet otherwise if requeued the job may enter an invalid
COMPLETING state.

select/cons_res plugin: Fix memory leak related to job preemption.
bug 837

This give system administrators the option on AMD Opteron 6000
series processors of either considering each NUMA node on a socket
as a separate socket (resulting in some incorrect logging of socket
count information) or not (resulting in sub-optimal job allocations
since each core in the socket will be considered equivalent, even
if on different NUMA nodes within the socket).
bug 838

not able to be separated into multiply patches.

If EnforcePartLimits=Yes and QOS job is using can override limits, allow
it.

Fix issues if partition allows or denys account's or QOS' and either are
not set.

If a job requests a partition and it doesn't allow a QOS or account the
job is requesting pend unless EnforcePartLimits=Yes.  Before it would
always kill the job at submit.

based on the mask given.

task/affinity.

thread in a core.

it can bind cyclically across sockets.

cpus-per-task support: Try to pack all CPUs of each tasks onto one socket.
Previous logic could spread the tasks CPUs across multiple sockets.

This reverts commit b22268d8.

Properly enforce job --requeue and --norequeue options. Previous
logic was in three places not doing so (either ignoring the value,
ANDing it with the JobRequeue configuration option or using the
JobRequeue configuration option by itself).
bug 821

Add SelectTypeParameters option of CR_PACK_NODES to pack a job's tasks
tightly on its allocated nodes rather than distributing them evenly across
the allocated nodes.
bug 819

something you also get a signal which would produce deadlock.

Fix Bug 601.

Run EpilogSlurmctld for a job is killed during slurmctld reconfiguration.
bug 806

Only if ALL of their partitions are hidden will a job be hidden by default.
bug 812

Correct SelectTypeParameters=CR_LLN with job selecition of specific nodes.
Previous logic would in most instances allocate resources on all nodes
to the job.