version of Slurm.

of at multifactor poll.

to drain the node and log error slurmd log file.

gres_alloc, gres_req, and gres_used fields were empty if the
job was not started immediately.
bug 380

accounting_storage/filetxt.

erroneously on a bluegene system.

message.

users.

values.

show information to users that had no associations on the system.

Fix for bug 330

Previously srun would fail if the hostlist expression was larger
than 0xffff bytes.

When using ThreadsPerCore > 1, it appears that DefMemPerCPU is being
scaled by slurmctld, but not by slurmd/slurmstepd.

For example, we set ThreadsPerCore=2 and DefMemPerCPU=100. Running a
single core job, we would expect two threads to be allocated and AllocMem
on the assigned node to increase by 200MB. scontrol reports that AllocMem
increased by 200MB, but the task/cgroup plugin only sees 100M of RAM.

It looks like the problem may lie in common/slurm_cred.c:format_core_allocs().
The function counts the job/step cores and multiplies the mem_limit's,
but it does not scale the CPU count like in slurmd/slurmd/req.c:_check_job_credential().
See bug 309

Effects jobs with --exclusive and --cpus-per-task options
bug 355

enum.

for as the job/step id.

The SLURM Makefile.am scripts use pkglibexecdir. One source indicates
that this was not added until automake 1.10.2
(https://github.com/rerun/rerun/issues/167).

So we just made that to be the minimum.

Under very heavy load with many thousands of batch job submissions
or job signals, the write lock can be held for very long periods of
time preventing job scheduling, squeue response, etc. This code
inserts a timing break to permit other functions to get the locks.