sbatch man pages

    option. Patches from Rod Schulz, Bull.

not all nodes have the same number of allocated CPUs.

    salloc, sbatch and srun man pages. These options are defunct, Patch from
    Rod Schultz, Bull.

   svn merge -r20596:20629 https://eris.llnl.gov/svn/slurm/branches/slurm-2.2.multi.partition

    srun/sbatch --hold/-H option or use "scontrol update jobid=# priority=0"
    to hold and "scontrol update jobid=# priority=1" to release).

    environment variables (if any) get propagated to the spawned job. This is
    particularly important for jobs that are submitted on one cluster and run
    on a different cluster.

    initiation will be delayed until all allocated nodes have booted. Salloc
    will log the delay with the messages "Waiting for nodes to boot" and "Nodes
    are ready for use". 

Added ability to view/modify a job's gres using scontrol.

    has been modified to display and modify the new field. sched/backfill
    plugin has been changed to alter time limits of jobs with the
    --time-min option if doing so permit earlier job initiation.

   a job or step receives a TERM or KILL signal

   preferred alternative to the "scontrol setdebug" command.

man pages

    --sockets-per-node, --cores-per-socket and --threads-per-core options.
    Remove --mincores, --minsockets, --minthreads options (map them to 
    minimum values of -sockets-per-node, --cores-per-socket and 
    --threads-per-core for now).

SLURM_IMMEDIATE_EXIT to SLURM_EXIT_IMMEDIATE

    to permit user control over exit codes so application exit codes can be
    distiguished from those generated by SLURM. SLURM_ERROR_EXIT specifies the
    exit code when a SLURM error occurs. SLURM_IMMEDIATE_EXIT specifies the 
    exit code when the --immediate option is specified and resources are not
    available. Any other non-zero exit code would be that of the application
    run by SLURM.