Remove duplicate backfill scheduling tests. For example there is
no need to test if a job can be started if the only difference
from the previous test involves nodes in other partitions that
can not be used by the job we are trying to start.

The backfill scheduler was always reporting the time that a job
was being considered as NOW rather than the time that was really
being considered.

decreases and total is less than in use.

This is a correction to commit 308b7432

Improve how failures in slurmd/slurmstepd communications are logged.

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

This will help limit damage from two active primary slurmctld
(split brain problem).

it is already running.

Duplicate triggers are not not allowed

Job profiling leaves a file open

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).

Replace printing of job_id using %d with %u

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.

A configuration change trigger event occurs when a node state
changes (e.g. Up, Down, Drain, etc.)

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.

If shutdown of the slurmctld daemon is in progress, then stop
trying to schedule jobs or process reconfigure requests. These
are the only operations that take a significant amount of time
and only service to slow down the shutdown process. We want the
daemon to stop processing incoming RPCs and save state as soon
as possible.