to front end nodes.

srun properly interprets a leading "." in the executable name based upon
the working directory of the compute node rather than the submit host.

script that will use it.

Note optional model type specification

The srun, salloc and sbatch man pages were not updated to describe
how to specify gres model types.

states.

srun --export variable check wrong

Fix sbatch --export=ALL, it was treated by srun as a request to explicitly
export only the environment variable named "ALL".
bug 1045

has finished)

Conflicts:
	META
	NEWS

Arguments in wrong order

timeout when talking to the Database is the same timeout so a race
condition could occur in the requesting client when receiving the response
if the database is unresponsive.

the entire cnode.

Under some conditions a step may be allocated fewer nodes than requested. Specifically, if the job uses the --exclusive --nodelist and in some fashion a higher node count, it may only be allocated the nodes in the specified node list. For example:
$ srun  -n2 --exclusive --ntasks-per-node=1 --cpus-per-task=4 -w smd1 hostname
smd1
smd1

This problem appears to only exist in version 14.11 and only applies to the step allocation, not the job allocation.