once)

is called right after startup and is sort of redundant, so the update
flag is better.

slurmctld.

bug 491

There need to be some network enhancements for proper operation
though.

Print an error message if an srun command specifies the --core-spec
option for a job step. It must be set at job allocation time (using
srun, salloc or sbatch). Note this is a difference in behavior from
Cray/ALPS systems, which don't even have job steps similar to Slurm.

count.

The slurm_complete_prolog() API originally in slurm.h and src/api
is not a user API and the logic has been moved directly into
src/slurmd/slurmd/req.c

nodes.

This data structure is internal to Slurm and should not be visible to users

Otherwise the existing enum values will change, breaking old code

select/cons_res bug fix for range of node counts with --cpus-per-task
option (e.g. "srun -N2-3 -c2 hostname" would allocate 2 CPUs on the first
node and 0 CPUs on the second node).

If a job requires specific nodes and can not run due to those nodes being
busy, the main scheduling loop will block those specific nodes rather than
the entire queue/partition.
bug 595

variable.

This reverts commit 1764a7e2.

Conflicts:

	NEWS

is not a corresponding association.

is not a corresponding association.

This corrects some of the logic in
commit e8b11948
There were several plugins storing the wrong plugin type code
(e.g. checkpoint/poe was recording state as checkpoint/blcr).
In addition, since there are new fields being stored, they
must be recorded as a different protocol_version, otherwise
all jobs would be lost when upgrading the system from an
earlier slurm release.