Expect timing was sometimes causing failures

File delays sometimes larger than 60 seconds

Conflicts:
	doc/man/man5/slurm.conf.5
	testsuite/expect/test1.89
	testsuite/expect/test1.90

Change Sockets to SocketsPerBoard and Procs to CPUs

If the backfill scheduler relinquishes locks and the normal job
scheduler starts a job that the backfill scheduler was actively
working, the backfill scheduler will try to re-schedule that
same job, possibly resulting in an invalid memory reference
or other badness.

Fix for --cpu_bind=map_cpu/mask_cpu/map_ldom/mask_ldom plus
--mem_bind=map_mem/mask_mem options, broken in 2.6.2.
See commit 718382da

Expect was failing periodicallly due to apparent timing problems

make sure we weren't the one holding things up.

A time value of "#-#" ignored the hour value (second #).

Corrections to commit dbbd78e2
Index into array was using global task count rather than local
task count

This corrects a bug introduced in
commit dbbd78e2
which went off the end of an array

This messsage type:
Warning: Note very large processing time from schedule: usec=9467365 began=11:06:23.003
is reporting the end time as the began value

In commit dbbd78e2
logic was added that, at least on some systems, lost flags needed
to distinguish between exit on signal and exit status code. This
resulted in test 7.13 failing on Ubuntu 13.04

Bug was introduced in commit b7e60b98
which resulting in job step ID being preinted by squeue incorrectly

Conflicts:
	src/slurmd/slurmd/slurmd.c

This prevents premature re-sending of job kill RPC
(e.g. "Resending TERMINATE_JOB request JobId=#")