This corrects logic in commit fae55cbe
to properly support front-end system configurations

Reset a node's CpuLoad value at least once each SlurmdTimeout seconds.
Previously the value would not be reset unless communications with the
slurmd did not happen for at least 1/3 of the SlurmdTimeout value.
That means nodes that were actively running and terminating jobs would
not get the CpuLoad value reset in a timely fashion. Added a CpuLoad
reset timer to prevent this.

Add logic to sleep and retry if slurm.conf can't be read.
Without this, the slurmd daemons may die and when the SlurmdTimeout
is reached, the nodes will be marked DOWN and their jobs will be
killed.
In the long term, it would be good to exit only if the read files
on program startup, and the daemons keep running with old configuration
on reconfiguration, but I don't have time to do that work now.

The function slurm_api_set_conf_file() is never referenced.
Remove it. No change in logic.

No change in logic. Just remove redundant function return code.

Fix invalid memory reference if script returns error message
for user. Previous code failed to set static variable to NULL
resulting in xfree of memory previously freed elsewhere.

Add requeuehold command to information generated by scontrol's
help command
bug 642

Conflicts:
	META
	NEWS

Add support for job array options in the qsub command, in #PBS
options for sbatch scripts and set the appropriate environment
variables in the spank_pbs plugin (PBS_ARRAY_ID and PBS_ARRAY_INDEX).
Note that Torque uses the "-t" option and PBS Pro uses the "-J"
option.

This would break the scenario where you want 64 tasks on each node, but
only want a total of 96 tasks, since --ntasks-per-node is a maximum, this
should be allowed.

slurm.conf.  Rebooting daemons after adding nodes to the slurm.conf
is highly recommended.

use the old version of state storage

Add a job flag to indicate when the EpilogSlurmctld us running
and don't purge the job record until it completes. This lets
the EpilogSlurmctld requeue the job and otherwise manage it.
bugs 635 and 636

Change warnings about slurm.conf configuration problems only for
1) user root, who is in a position to do something about this OR
2) other users only if they use the "-vv" (very verbose option)
bug 639

bug 640