Generate an error return rather than fatal error and exit if the
configuraiton file is absent or invalid. This will permit Slurm APIs to be
more reliably used by other programs.
bug 374

to drain the node and log error slurmd log file.

MaxBlockInError set the job wait reason appropriately.

Just a bunch of empty functions now. See bug 77

%_with_cray to %_with_cray_alps.

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.

This reverts the following two commits:
d84bdaea
25051e48
While they work as designed, we probably do not want to provide
support for the DenyGroups option

The AllowGroups and DenyGroups configuration parameters only apply
to the effective group ID of the job. Previously any user with
access to any allowed group was permitted to use the partition.

AllowAccounts, AllowQOS, DenyAccounts, DenyGroups and DenyQOS.
Enforcement logic needs to be added as well as slurm.conf man page.

message.

users.

Processes which can be signalled will be. Others will be signalled
when possible from a pthread.

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