Response to bug 274

If a user requests multiple counts of a specific GRES type (e.g.
"--gres=gpu:2") and those GRES are associated with specific CPUs,
the job submit could fail without this change.

Conflicts:
	testsuite/expect/test1.90

Make test work if current working directory not in the search path
Check for appropriate task rank on POE based systems
Disable the entire test on POE systems

The option "interval" was the original parameter, but has not been
documented for a year or more.

Without this change pmdv12 was bound to one CPU and could not use
all of the resources allocated to the job step for the tasks that
it launches

This only changes behaviour when the --ntasks option is not used,
but the --cpus-per-task option is use

Also add size specification of "%0" to not limit a field size.
For example "sacct --format=%0ALL" to print everything.

we used cpus erroneously but now we use tasks.  The cpus variable will
be taken out in 2.6.

also "-euidevice sn_single".

Make sure the lock array in assoc_mgr.h matches that of locks.h
See commit 2e99b99a

cluster.

disk IO.