The man page for slurm.conf, select/cons_res parameter SelectTypeParameters, values CR_Socket and CR_Socket_Memory states the following:

"Note that jobs requesting one CPU will only be given access to that one CPU"

I think this statement is incorrect, or at least very misleading to users. A job requesting one CPU will only be allocated one CPU, but unless task/affinity is enabled or some other CPU binding mechanism is used, the job can access all of the CPUs on the node.  That is, a task that is distributed to the node can run on any of the CPUs on the node, not just on the one CPU that was allocated to its job. I propose the following patch to replace "given access to" with "allocated".

Regards,
Martin Perry

    a full midplane on BlueGene computers. Treat cnodes as liceses which can
    be reserved and are consumed by jobs.

sbatch man pages

    option. Patches from Rod Schulz, Bull.

scheduling is configured.

  slurm.conf man page

Miscellaneous typos, found while reading documentation.

The majority is in the manpages and within comments, only one occurrence
is in an error message (function name of set_node_down).

   the exit code of the job script (or salloc) while derived_ec contains the
   highest exit code of all the job steps.
-- Added SLURM_JOB_EXIT_CODE and SLURM_JOB_DERIVED_EC variables to the
   EpilogSlurmctld environment

    future that the backfill scheduler will look when considering jobs to start.
    The default value is one day. See "man slurm.conf" for details.

    BASIL on Cray computers.

previously supported).

    many jobs on queue should be tested for attempted scheduling when a job
    completes or other routine events. Default value is 100 jobs. The full job
    queue is tested on a less frequent basis. This option can dramatically
    improve performance on systems with thousands of queued jobs.

    to backfill schedule if slurmctld has more than 5 active RPCs.

    DOWN nodes.

 (the plugin is optional).
Let resource counts be specified with a "K" or "M" suffix.

    job at submission time, but to attempt scheduling many jobs at once for
    improved performance under heavy load.

    than one port for improved scalability.

    reservations.

    allocation created using the salloc or srun command if those commands
    cease responding for the InactiveLimit regardless of any running job steps.
    This parameter will no longer effect jobs spawned using sbatch.

to become effective.

    The default MaxJobCount was changed from 5,000 to 10,000.

Patch for adding CR_CORE_DEFAULT_DIST_BLOCK as a select option to layout jobs using block layout across cores within each node instead of cyclic which was previously the default.