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

67fdbce5

When a batch job requeue completes, clear it's bitmap of completing
nodes. If the bitmap were to persist, and nodes are added/remove in
slurm.conf, and "scontrol reconfigure" is executed, and one of the
bits in that bitmap now point to a DOWN node, avoid killing the job.
bug 805

If a batch job is discovered to be missing from it's head node, set its exit code to 1 rather than leaving it as zero.
Bug 833

Was printing unsigned as int

compiler would treat 1 as a 32 bit number and wrap.

more of a hey, the user is asking for something out of the norm.

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.

This reverts commit 859839a7
The ntasks_per_core option was previously really treated like number of CPUs (rather than tasks) to allocate per core, which seems to be what is desired.

wait for.

based on the mask given.

task/affinity.

thread in a core.

it can bind cyclically across sockets.

Previous logic assumed cpus_per_task=1, so ntasks_per_core option
could spread the job across more cores than desired

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.

Previous logic was counting CPUs, but assuming each task would
only use one CPU.

This reverts commit b22268d8.

Conflicts:
	src/slurmctld/job_mgr.c

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

There should be no change in behavior with the production code,
but this will improve the robustness of the code if someone makes
changes to the logic.

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.