to drain the node and log error slurmd log file.

at debug() level, make the argument check case insensitive,
avoid printing duplicate \n.

Similar problem to that described in bug 343 for sbatch
There are many differences in the salloc/srun/sbatch argument
processing that should probably be made more uniform, but no time
to do so now

and max_nodes == min_nodes or no max_nodes specified
bug introduced in commit 1b7f5b91
fix for bug 343

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

This results in the srun command logging the plugin load when gres/gpu
is used, which the user will not want to see.
Introduced in commit 9f9b3407

If a job preemption involves multiple preemption types (cancel +
requeue + suspend) and more than one job is preempted with one
of the preemption types being suspend and the other something else,
the preemptee initiation may be delayed longer than needed.
bug 377

such that  1) specifying --without-rrdtool or --with-rrdtool=no works as
expected, disabling rrdtool build and  2) the link test also tests for
rrd_info_t which was not present in the old rrdtool-devel-1.2.27 which I
happen to have installed. It is present in the newer rrdtool I used from
rpmforge for centos5 rrdtool-devel-1.4.7-1.el5.rf.x86_64.
rrd_info_t was chosen because it was in the output of make when it failed.

That is I saw this error:
/bin/sh ../../../../libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../../.. -I../../../../slurm -I../../../.. -I../../../../src/common  -I/usr/include    -DNUMA_VERSION1_COMPATIBILITY -g -O2 -pthread -fno-gcse -MT ext_sensors_rrd.lo -MD -MP -MF .deps/ext_sensors_rrd.Tpo -c -o ext_sensors_rrd.lo ext_sensors_rrd.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../../.. -I../../../../slurm -I../../../.. -I../../../../src/common -I/usr/include -DNUMA_VERSION1_COMPATIBILITY -g -O2 -pthread -fno-gcse -MT ext_sensors_rrd.lo -MD -MP -MF .deps/ext_sensors_rrd.Tpo -c ext_sensors_rrd.c  -fPIC -DPIC -o .libs/ext_sensors_rrd.o
ext_sensors_rrd.c: In function '_rrd_get_last_one':
ext_sensors_rrd.c:198: error: 'rrd_info_t' undeclared (first use in this function)
ext_sensors_rrd.c:198: error: (Each undeclared identifier is reported only once
ext_sensors_rrd.c:198: error: for each function it appears in.)
ext_sensors_rrd.c:198: error: 'data' undeclared (first use in this function)
ext_sensors_rrd.c:198: error: 'data_p' undeclared (first use in this function)

that was fixed in f1c74d6e

Jobs could be initiated out of order if
1. Priority/basic configured AND
2. Sched/builtin (First-in First-out) configured AND
3. Job preemption configured AND
4. Multiple partitions with different priorities
bug 373