Add SLURM_CLUSTER_NAME to environment variables passed to PrologSlurmctld,
Prolog, EpilogSlurmctld, and Epilog.

Previous logic never reopened the file, preventing proper functioning
of logrotate.

Use hash function to locate job records for improved performance.

Change partition write lock to a read lock as we use a different
mechanism for hidden partitions in getting individual jobs.

Correct logic returning remaining job dependencies in job information
reported by scontrol and squeue. Eliminates vestigial descriptors with
no job ID values (e.g. "afterany"). As depdencies are removed, the
job ID values were removed from the strings, but not the descriptors.
This eliminates both. It also checks the full job ID to make sure we do
not remove "afterany:1234" when job "123" completes.

Fix race condition on batch job termination that could result in a job exit
code of 0xfffffffe if the slurmd on node zero registers its active jobs at
the same time that slurmstepd is recording the job's exit code.
but 535

proctrack/cgroup - Add locking to prevent race condition where one job step
is ending for a user or job at the same time another job stepsis starting
and the user or job container is deleted from under the starting job step.
bug 447

Substantial performance improvement for systems with Shared=YES or FORCE
and large numbers of running jobs (replace bubble sort with quick sort).
Bug 525

Original code worked only for Cray systems. For other systems it
set gres_alloc to the total number of each GRES allocated on each
node to any job

Original code worked only for Cray systems. For other systems it
set gres_alloc to the total number of each GRES allocated on each
node to any job

limits are configured as 0.

bug 511

Add ability to clear a node's DRAIN flag using scontrol or sview by setting
it's state to "UNDRAIN". The node's base state (e.g. "DOWN" or "IDLE") will
not be changed.
bug 514

bug 511

This might have worked fine for core reservations or when there
are sufficient idle nodes to use, the the select_g_resv_test()
function clears the node bitmap for nodes that it can not use
and the reservation create logic did not restore that bitmap
after a failed resource selection attempt. This logic restores
the node bitmap on a failed call to select_g_resv_test() so we
can add nodes to the bitmap of available nodes rather than having
it repeatedly cleared.
The logic also adds some performance enhancements that I will
add to in the next commit.

This fixes a bug where a system is enforcing memory limits and
the job already has a step running on some of the nodes then
tries to start another step using some of those nodes. For example
wwith DefMemPerNode configured and the select plugin enforcing
memory limits, try:
salloc -N2 bash
$ srun -N1 sleep 10&
$ srun -N2 hostname
Without this patch, the second srun would fail instead of pend.

Correction to hostlist parsing bug introduced in v2.6.4 for hostlists with
more than one numeric range in brackets (e.g. rack[0-3]_blade[0-63]").
bug505

Just a start for now

Added -S/--core-spec option to salloc, sbatch and srun commands to reserve
    specialized cores for system use. Modify sview and scontrol to set/get
    core_spec
struct job_info / slurm_job_info_t: Added core_spec
struct job_descriptorjob_desc_msg_t: Added core_spec

The system really can not handle larger job arrays without adding
a job array data structure, but this puts some of the infrastructure
in place now.

to offer a greater priority range based upon utilization.

Add argument to priority plugin's priority_p_reconfig function to note
when the association and QOS used_cpu_run_secs field has been reset.
Without this flag, we remove time on "scontrol setdebug" or
"scontrol setdebugflag" that can result in used_cpu_run_secs
going negative or otherwise get bad values.
Correction to logic added in commit 6d793189
bug 423

Add argument to priority plugin's priority_p_reconfig function to note
when the association and QOS used_cpu_run_secs field has been reset.
Without this flag, we remove time on "scontrol setdebug" or
"scontrol setdebugflag" that can result in used_cpu_run_secs
going negative or otherwise get bad values.
Correction to logic added in commit 6d793189
bug 423