Conflicts:
	META

This is due to a bug introduced in commit 83d626caa
SOme configurations could result in NULL names in the node list table
(e.g. hidden partitions).

SLowness introduced in commit 83d626ca

This reverts commit 0d6a9965
That patch would permit a job with shared resources to run on
the same node as a job without shared resources, unfortunately
it let those jobs share CPUs. Finer grained sharing might be
possible with extensive code changes, but not something to
work on now.

Without this change, the job's --shared option when used with a partition
configuration of Shared=YES was not being honored by the select/cons_res
or select/serial plugin.

Original code was implicitly setting a job's shared field to 1
for select/cons_res.

This reverts commit c773b750

Conflicts:
	META
	NEWS

display larger sharing values.

cores specialization test 17.34 failed with bad assignment logic

including state, job ids and allocated nodes counter.

Message was possibly misleading as specialized cores can be
requested by users, which differ from the configured counts.

Provide more precise error message when job allocation can not be satisfied
(e.g. memory, disk, cpu count, etc. rather than just "node configuration
not available").
bug 836

If FastSchedule=0 is configured and some nodes have not registered
for service (so we do not know their actual resource counts), then
leave the job pending rather than rejecting it without knowing if
it can run later (when the node registers and we know its specs).
bug 872

Conflicts:
	src/common/slurm_protocol_defs.c