neulab/tldr huggingface dataset:
--gid=<group> If srun is run as root, and the --gid option is used, submit the job with group's group access permissions.  group may be the group name or the numerical group ID. This option applies to job allocations.
--gpus-per-socket=[<type>:]<number> Specify the number of GPUs required for the job on each socket included in the job's resource allocation.  An optional GPU type specification can be supplied.  For example "--gpus-per-socket=volta:3".  Multiple options can be requested in a comma separated list, for example: "--gpus-per-socket=volta:3,kepler:1".  Requires job to specify a sockets per node count ( --sockets-per-node).  See also the --gpus, --gpus-per-node and --gpus-per-task options.  This option applies to job allocations.
--gres=<list> Specifies a comma delimited list of generic consumable resources. The format of each entry on the list is "name[[:type]:count]". The name is that of the consumable resource.  The count is the number of those resources with a default value of 1.  The count can have a suffix of "k" or "K" (multiple of 1024), "m" or "M" (multiple of 1024 x 1024), "g" or "G" (multiple of 1024 x 1024 x 1024), "t" or "T" (multiple of 1024 x 1024 x 1024 x 1024), "p" or "P" (multiple of 1024 x 1024 x 1024 x 1024 x 1024).  The specified resources will be allocated to the job on each node.  The available generic consumable resources is configurable by the system administrator.  A list of available generic consumable resources will be printed and the command will exit if the option argument is "help".  Examples of use include "--gres=gpu:2,mic:1", "--gres=gpu:kepler:2", and "--gres=help".  NOTE: This option applies to job and step allocations. By default, a job step is allocated all of the generic resources that have been allocated to the job.  To change the behavior so that each job step is allocated no generic resources, explicitly set the value of --gres to specify zero counts for each generic resource OR set "--gres=none" OR set the SLURM_STEP_GRES environment variable to "none".
--gres-flags=<type> Specify generic resource task binding options.  This option applies to job allocations.
-H, --hold Specify the job is to be submitted in a held state (priority of zero).  A held job can now be released using scontrol to reset its priority (e.g. "scontrol release <job_id>"). This option applies to job allocations.
--hint=<type> Bind tasks according to application hints. NOTE: This option cannot be used in conjunction with any of --ntasks-per-core, --threads-per-core, --cpu-bind (other than --cpu-bind=verbose) or -B. If --hint is specified as a command line argument, it will take precedence over the environment.
-I, --immediate[=<seconds>] exit if resources are not available within the time period specified.  If no argument is given (seconds defaults to 1), resources must be available immediately for the request to succeed. If defer is configured in SchedulerParameters and seconds=1 the allocation request will fail immediately; defer conflicts and takes precedence over this option.  By default, --immediate is off, and the command will block until resources become available. Since this option's argument is optional, for proper parsing the single letter option must be followed immediately with the value and not include a space between them. For example "-I60" and not "-I 60". This option applies to job and step allocations.
-i, --input=<mode> Specify how stdin is to redirected. By default, srun redirects stdin from the terminal all tasks. See IO Redirection below for more options.  For OS X, the poll() function does not support stdin, so input from a terminal is not possible. This option applies to job and step allocations.
-J, --job-name=<jobname> Specify a name for the job. The specified name will appear along with the job id number when querying running jobs on the system. The default is the supplied executable program's name. NOTE: This information may be written to the slurm_jobacct.log file. This file is space delimited so if a space is used in the jobname name it will cause problems in properly displaying the contents of the slurm_jobacct.log file when the sacct command is used. This option applies to job and step allocations.
--jobid=<jobid> Initiate a job step under an already allocated job with job id id. Using this option will cause srun to behave exactly as if the SLURM_JOB_ID environment variable was set. This option applies to step allocations.
-K, --kill-on-bad-exit[=0|1] Controls whether or not to terminate a step if any task exits with a non-zero exit code. If this option is not specified, the default action will be based upon the Slurm configuration parameter of KillOnBadExit. If this option is specified, it will take precedence over KillOnBadExit. An option argument of zero will not terminate the job. A non-zero argument or no argument will terminate the job.  Note: This option takes precedence over the -W, --wait option to terminate the job immediately if a task exits with a non-zero exit code.  Since this option's argument is optional, for proper parsing the single letter option must be followed immediately with the value and not include a space between them. For example "-K1" and not "-K 1".
-k, --no-kill [=off] Do not automatically terminate a job if one of the nodes it has been allocated fails. This option applies to job and step allocations.  The job will assume all responsibilities for fault-tolerance.  Tasks launch using this option will not be considered terminated (e.g. -K, --kill-on-bad-exit and -W, --wait options will have no effect upon the job step).  The active job step (MPI job) will likely suffer a fatal error, but subsequent job steps may be run if this option is specified.
Specify an optional argument of "off" disable the effect of the SLURM_NO_KILL environment variable.
The default action is to terminate the job upon node failure.
-l, --label Prepend task number to lines of stdout/err.  The --label option will prepend lines of output with the remote task id. This option applies to step allocations.
-L, --licenses=<license> Specification of licenses (or other resources available on all nodes of the cluster) which must be allocated to this job. License names can be followed by a colon and count (the default count is one).  Multiple license names should be comma separated (e.g.  "--licenses=foo:4,bar"). This option applies to job allocations.
-M, --clusters=<string> Clusters to issue commands to.  Multiple cluster names may be comma separated.  The job will be submitted to the one cluster providing the earliest expected job initiation time. The default value is the current cluster. A value of 'all' will query to run on all clusters.  Note the --export option to control environment variables exported between clusters.  This option applies only to job allocations.  Note that the SlurmDBD must be up for this option to work properly.
-m, --distribution= *|block|cyclic|arbitrary|plane=<options> [:*|block|cyclic|fcyclic[:*|block| cyclic|fcyclic]][,Pack|NoPack]
Specify alternate distribution methods for remote processes.  This option controls the distribution of tasks to the nodes on which resources have been allocated, and the distribution of those resources to tasks for binding (task affinity). The first distribution method (before the first ":") controls the distribution of tasks to nodes.  The second distribution method (after the first ":") controls the distribution of allocated CPUs across sockets for binding to tasks. The third distribution method (after the second ":") controls the distribution of allocated CPUs across cores for binding to tasks.  The second and third distributions apply only if task affinity is enabled.  The third distribution is supported only if the task/cgroup plugin is configured. The default value for each distribution type is specified by *.
Note that with select/cons_res and select/cons_tres, the number of CPUs allocated to each socket and node may be different. Refer to https://slurm.schedmd.com/mc_support.html for more information on resource allocation, distribution of tasks to nodes, and binding of tasks to CPUs. First distribution method (distribution of tasks across nodes):
*      Use the default method for distributing tasks to nodes (block).
arbitrary The arbitrary method of distribution will allocate processes in-order as listed in file designated by the environment variable SLURM_HOSTFILE.  If this variable is listed it will over ride any other method specified.  If not set the method will default to block.  Inside the hostfile must contain at minimum the number of hosts requested and be one per line or comma separated.  If specifying a task count (-n, --ntasks=<number>), your tasks will be laid out on the nodes in the order of the file. NOTE: The arbitrary distribution option on a job allocation only controls the nodes to be allocated to the job and not the allocation of CPUs on those nodes. This option is meant primarily to control a job step's task layout in an existing job allocation for the srun command. NOTE: If the number of tasks is given and a list of requested nodes is also given, the number of nodes used from that list will be reduced to match that of the number of tasks if the number of nodes in the list is greater than the number of tasks.
Second distribution method (distribution of CPUs across sockets for binding):
*      Use the default method for distributing CPUs across sockets (cyclic).
block  The block distribution method will distribute allocated CPUs consecutively from the same socket for binding to tasks, before using the next consecutive socket.
cyclic The cyclic distribution method will distribute allocated CPUs for binding to a given task consecutively from the same socket, and from the next consecutive socket for the next task, in a round-robin fashion across sockets.
fcyclic The fcyclic distribution method will distribute allocated CPUs for binding to tasks from consecutive sockets in a round-robin fashion across the sockets.
Third distribution method (distribution of CPUs across cores for binding):
*      Use the default method for distributing CPUs across cores (inherited from second distribution method).
block  The block distribution method will distribute allocated CPUs consecutively from the same core for binding to tasks, before using the next consecutive core.
cyclic The cyclic distribution method will distribute allocated CPUs for binding to a given task consecutively from the same core, and from the next consecutive core for the next task, in a round-robin fashion across cores.
fcyclic The fcyclic distribution method will distribute allocated CPUs for binding to tasks from consecutive cores in a round-robin fashion across the cores.
Optional control for task distribution over nodes:
Pack   Rather than evenly distributing a job step's tasks evenly across its allocated nodes, pack them as tightly as possible on the nodes.  This only applies when the "block" task distribution method is used.
NoPack Rather than packing a job step's tasks as tightly as possible on the nodes, distribute them evenly.  This user option will supersede the SelectTypeParameters CR_Pack_Nodes configuration parameter.
--mail-type=<type> Notify user by email when certain event types occur.  Valid type values are NONE, BEGIN, END, FAIL, REQUEUE, ALL (equivalent to BEGIN, END, FAIL, INVALID_DEPEND, REQUEUE, and STAGE_OUT), INVALID_DEPEND (dependency never satisfied), STAGE_OUT (burst buffer stage out and teardown completed), TIME_LIMIT, TIME_LIMIT_90 (reached 90 percent of time limit), TIME_LIMIT_80 (reached 80 percent of time limit), and TIME_LIMIT_50 (reached 50 percent of time limit).  Multiple type values may be specified in a comma separated list.  The user to be notified is indicated with --mail-user. This option applies to job allocations.
--mail-user=<user> User to receive email notification of state changes as defined by --mail-type.  The default value is the submitting user. This option applies to job allocations.
--mcs-label=<mcs> Used only when the mcs/group plugin is enabled.  This parameter is a group among the groups of the user.  Default value is calculated by the Plugin mcs if it's enabled. This option applies to job allocations.
--mem=<size[units]> Specify the real memory required per node.  Default units are megabytes.  Different units can be specified using the suffix [K|M|G|T].  Default value is DefMemPerNode and the maximum value is MaxMemPerNode. If configured, both of parameters can be seen using the scontrol show config command.  This parameter would generally be used if whole nodes are allocated to jobs (SelectType=select/linear).  Specifying a memory limit of zero for a job step will restrict the job step to the amount of memory allocated to the job, but not remove any of the job's memory allocation from being available to other job steps.  Also see --mem-per-cpu and --mem-per-gpu.  The --mem, --mem-per-cpu and --mem-per-gpu options are mutually exclusive. If --mem, --mem-per-cpu or --mem-per-gpu are specified as command line arguments, then they will take precedence over the environment (potentially inherited from salloc or sbatch).
NOTE: A memory size specification of zero is treated as a special case and grants the job access to all of the memory on each node for newly submitted jobs and all available job memory to new job steps.
Specifying new memory limits for job steps are only advisory.
If the job is allocated multiple nodes in a heterogeneous cluster, the memory limit on each node will be that of the node in the allocation with the smallest memory size (same limit will apply to every node in the job's allocation).
--mem-per-cpu=<size[units]> Minimum memory required per allocated CPU.  Default units are megabytes.  Different units can be specified using the suffix [K|M|G|T].  The default value is DefMemPerCPU and the maximum value is MaxMemPerCPU (see exception below). If configured, both parameters can be seen using the scontrol show config command. Note that if the job's --mem-per-cpu value exceeds the configured MaxMemPerCPU, then the user's limit will be treated as a memory limit per task; --mem-per-cpu will be reduced to a value no larger than MaxMemPerCPU; --cpus-per-task will be set and the value of --cpus-per-task multiplied by the new --mem-per-cpu value will equal the original --mem-per-cpu value specified by the user. This parameter would generally be used if individual processors are allocated to jobs (SelectType=select/cons_res).  If resources are allocated by core, socket, or whole nodes, then the number of CPUs allocated to a job may be higher than the task count and the value of --mem-per-cpu should be adjusted accordingly.  Specifying a memory limit of zero for a job step will restrict the job step to the amount of memory allocated to the job, but not remove any of the job's memory allocation from being available to other job steps.  Also see --mem and --mem-per-gpu.  The --mem, --mem-per-cpu and --mem-per-gpu options are mutually exclusive.
--mem-bind=[{quiet,verbose},]type Bind tasks to memory. Used only when the task/affinity plugin is enabled and the NUMA memory functions are available.  Note that the resolution of CPU and memory binding may differ on some architectures. For example, CPU binding may be performed at the level of the cores within a processor while memory binding will be performed at the level of nodes, where the definition of "nodes" may differ from system to system.  By default no memory binding is performed; any task using any CPU can use any memory. This option is typically used to ensure that each task is bound to the memory closest to its assigned CPU. The use of any type other than "none" or "local" is not recommended.  If you want greater control, try running a simple test code with the options "--cpu-bind=verbose,none --mem-bind=verbose,none" to determine the specific configuration.
nosort avoid sorting free cache pages (default, LaunchParameters configuration parameter can override this default)
--mincpus=<n> Specify a minimum number of logical cpus/processors per node. This option applies to job allocations.
--msg-timeout=<seconds> Modify the job launch message timeout.  The default value is MessageTimeout in the Slurm configuration file slurm.conf. Changes to this are typically not recommended, but could be useful to diagnose problems.  This option applies to job allocations.
--mpi=<mpi_type> Identify the type of MPI to be used. May result in unique initiation procedures.
list   Lists available mpi types to choose from.
pmi2   To enable PMI2 support. The PMI2 support in Slurm works only if the MPI implementation supports it, in other words if the MPI has the PMI2 interface implemented. The --mpi=pmi2 will load the library lib/slurm/mpi_pmi2.so which provides the server side functionality but the client side must implement PMI2_Init() and the other interface calls.
pmix   To enable PMIx support (https://pmix.github.io). The PMIx support in Slurm can be used to launch parallel applications (e.g. MPI) if it supports PMIx, PMI2 or PMI1. Slurm must be configured with pmix support by passing "--with-pmix=<PMIx installation path>" option to its "./configure" script.
At the time of writing PMIx is supported in Open MPI starting from version 2.0.  PMIx also supports backward compatibility with PMI1 and PMI2 and can be used if MPI was configured with PMI2/PMI1 support pointing to the PMIx library ("libpmix").  If MPI supports PMI1/PMI2 but doesn't provide the way to point to a specific implementation, a hack'ish solution leveraging LD_PRELOAD can be used to force "libpmix" usage.
none   No special MPI processing. This is the default and works with many other versions of MPI.
This option applies to step allocations.
--multi-prog Run a job with different programs and different arguments for each task. In this case, the executable program specified is actually a configuration file specifying the executable and arguments for each task. See MULTIPLE PROGRAM CONFIGURATION below for details on the configuration file contents. This option applies to step allocations.
-N, --nodes=<minnodes[-maxnodes]> Request that a minimum of minnodes nodes be allocated to this job. A maximum node count may also be specified with maxnodes.  If only one number is specified, this is used as both the minimum and maximum node count.  The partition's node limits supersede those of the job.  If a job's node limits are outside of the range permitted for its associated partition, the job will be left in a PENDING state.  This permits possible execution at a later time, when the partition limit is changed.  If a job node limit exceeds the number of nodes configured in the partition, the job will be rejected.  Note that the environment variable SLURM_JOB_NUM_NODES (and SLURM_NNODES for backwards compatibility) will be set to the count of nodes actually allocated to the job. See the ENVIRONMENT VARIABLES section for more information.  If -N is not specified, the default behavior is to allocate enough nodes to satisfy the requirements of the -n and -c options.  The job will be allocated as many nodes as possible within the range specified and without delaying the initiation of the job.  If the number of tasks is given and a number of requested nodes is also given, the number of nodes used from that request will be reduced to match that of the number of tasks if the number of nodes in the request is greater than the number of tasks.  The node count specification may include a numeric value followed by a suffix of "k" (multiplies numeric value by 1,024) or "m" (multiplies numeric value by 1,048,576). This option applies to job and step allocations.
-n, --ntasks=<number> Specify the number of tasks to run. Request that srun allocate resources for ntasks tasks.  The default is one task per node, but note that the --cpus-per-task option will change this default. This option applies to job and step allocations.
In all cases the job allocation request must specify the --exclusive option and the step cannot specify the --overlap option.  Otherwise the request will be denied.
BULK_XFER[=<resources>] Enable bulk transfer of data using Remote Direct- Memory Access (RDMA).  The optional resources specification is a numeric value which can have a suffix of "k", "K", "m", "M", "g" or "G" for kilobytes, megabytes or gigabytes.  NOTE: The resources specification is not supported by the underlying IBM infrastructure as of Parallel Environment version 2.2 and no value should be specified at this time.  The devices allocated to a job must all be of the same type.  The default value depends upon depends upon what hardware is available and in order of preferences is IPONLY (which is not considered in User Space mode), HFI, IB, HPCE, and KMUX.
--ntasks-per-core=<ntasks> Request the maximum ntasks be invoked on each core.  This option applies to the job allocation, but not to step allocations.  Meant to be used with the --ntasks option.  Related to --ntasks-per-node except at the core level instead of the node level.  Masks will automatically be generated to bind the tasks to specific cores unless --cpu-bind=none is specified.  NOTE: This option is not supported unless SelectType=cons_res is configured (either directly or indirectly on Cray systems) along with the node's core count.
--ntasks-per-node=<ntasks> Request that ntasks be invoked on each node.  If used with the --ntasks option, the --ntasks option will take precedence and the --ntasks-per-node will be treated as a maximum count of tasks per node.  Meant to be used with the --nodes option.  This is related to --cpus-per-task=ncpus, but does not require knowledge of the actual number of cpus on each node.  In some cases, it is more convenient to be able to request that no more than a specific number of tasks be invoked on each node.  Examples of this include submitting a hybrid MPI/OpenMP app where only one MPI "task/rank" should be assigned to each node while allowing the OpenMP portion to utilize all of the parallelism present in the node, or submitting a single setup/cleanup/monitoring job to each node of a pre-existing allocation as one step in a larger job script. This option applies to job allocations.
--ntasks-per-socket=<ntasks> Request the maximum ntasks be invoked on each socket.  This option applies to the job allocation, but not to step allocations.  Meant to be used with the --ntasks option.  Related to --ntasks-per-node except at the socket level instead of the node level.  Masks will automatically be generated to bind the tasks to specific sockets unless --cpu-bind=none is specified.  NOTE: This option is not supported unless SelectType=cons_res is configured (either directly or indirectly on Cray systems) along with the node's socket count.
-O, --overcommit Overcommit resources. This option applies to job and step allocations.  When applied to job allocation, only one CPU is allocated to the job per node and options used to specify the number of tasks per node, socket, core, etc.  are ignored.  When applied to job step allocations (the srun command when executed within an existing job allocation), this option can be used to launch more than one task per CPU.  Normally, srun will not allocate more than one process per CPU.  By specifying --overcommit you are explicitly allowing more than one process per CPU. However no more than MAX_TASKS_PER_NODE tasks are permitted to execute per node.  NOTE: MAX_TASKS_PER_NODE is defined in the file slurm.h and is not a variable, it is set at Slurm build time.
--overlap Allow steps to overlap each other on the same resources. By default steps do not share resources with other parallel steps.
-o, --output=<filename pattern> Specify the "filename pattern" for stdout redirection. By default in interactive mode, srun collects stdout from all tasks and sends this output via TCP/IP to the attached terminal. With --output stdout may be redirected to a file, to one file per task, or to /dev/null. See section IO Redirection below for the various forms of filename pattern.  If the specified file already exists, it will be overwritten.
If --error is not also specified on the command line, both stdout and stderr will directed to the file specified by --output. This option applies to job and step allocations.
--open-mode=<append|truncate> Open the output and error files using append or truncate mode as specified.  For heterogeneous job steps the default value is "append".  Otherwise the default value is specified by the system configuration parameter JobFileAppend. This option applies to job and step allocations.
--het-group=<expr> Identify each component in a heterogeneous job allocation for which a step is to be created. Applies only to srun commands issued inside a salloc allocation or sbatch script.  <expr> is a set of integers corresponding to one or more options offsets on the salloc or sbatch command line.  Examples: "--het-group=2", "--het-group=0,4", "--het-group=1,3-5".  The default value is --het-group=0.
-p, --partition=<partition_names> Request a specific partition for the resource allocation.  If not specified, the default behavior is to allow the slurm controller to select the default partition as designated by the system administrator. If the job can use more than one partition, specify their names in a comma separate list and the one offering earliest initiation will be used with no regard given to the partition name ordering (although higher priority partitions will be considered first).  When the job is initiated, the name of the partition used will be placed first in the job record partition string. This option applies to job allocations.
--power=<flags> Comma separated list of power management plugin options. Currently available flags include: level (all nodes allocated to the job should have identical power caps, may be disabled by the Slurm configuration option PowerParameters=job_no_level).  This option applies to job allocations.
--priority=<value> Request a specific job priority.  May be subject to configuration specific constraints.  value should either be a numeric value or "TOP" (for highest possible value).  Only Slurm operators and administrators can set the priority of a job.  This option applies to job allocations only.
--profile=<all|none|[energy[,|task[,|filesystem[,|network]]]]> enables detailed data collection by the acct_gather_profile plugin.  Detailed data are typically time-series that are stored in an HDF5 file for the job or an InfluxDB database depending on the configured plugin.
Filesystem Filesystem data is collected.
--prolog=<executable> srun will run executable just before launching the job step.  The command line arguments for executable will be the command and arguments of the job step.  If executable is "none", then no srun prolog will be run. This parameter overrides the SrunProlog parameter in slurm.conf. This parameter is completely independent from the Prolog parameter in slurm.conf. This option applies to job allocations.
--pty  Execute task zero in pseudo terminal mode.  Implicitly sets --unbuffered.  Implicitly sets --error and --output to /dev/null for all tasks except task zero, which may cause those tasks to exit immediately (e.g. shells will typically exit immediately in that situation).  This option applies to step allocations.
-q, --qos=<qos> Request a quality of service for the job.  QOS values can be defined for each user/cluster/account association in the Slurm database.  Users will be limited to their association's defined set of qos's when the Slurm configuration parameter, AccountingStorageEnforce, includes "qos" in its definition. This option applies to job allocations.
-Q, --quiet Suppress informational messages from srun. Errors will still be displayed. This option applies to job and step allocations.
--quit-on-interrupt Quit immediately on single SIGINT (Ctrl-C). Use of this option disables the status feature normally available when srun receives a single Ctrl-C and causes srun to instead immediately terminate the running job. This option applies to step allocations.
-r, --relative=<n> Run a job step relative to node n of the current allocation.  This option may be used to spread several job steps out among the nodes of the current job. If -r is used, the current job step will begin at node n of the allocated nodelist, where the first node is considered node 0.  The -r option is not permitted with -w or -x option and will result in a fatal error when not running within a prior allocation (i.e. when SLURM_JOB_ID is not set). The default for n is 0. If the value of --nodes exceeds the number of nodes identified with the --relative option, a warning message will be printed and the --relative option will take precedence. This option applies to step allocations.
--reboot Force the allocated nodes to reboot before starting the job.  This is only supported with some system configurations and will otherwise be silently ignored. Only root, SlurmUser or admins can reboot nodes. This option applies to job allocations.
--resv-ports[=count] Reserve communication ports for this job. Users can specify the number of port they want to reserve. The parameter MpiParams=ports=12000-12999 must be specified in slurm.conf. If not specified and Slurm's OpenMPI plugin is used, then by default the number of reserved equal to the highest number of tasks on any node in the job step allocation.  If the number of reserved ports is zero then no ports is reserved.  Used for OpenMPI. This option applies to job and step allocations.
-s, --oversubscribe The job allocation can over-subscribe resources with other running jobs.  The resources to be over-subscribed can be nodes, sockets, cores, and/or hyperthreads depending upon configuration.  The default over-subscribe behavior depends on system configuration and the partition's OverSubscribe option takes precedence over the job's option.  This option may result in the allocation being granted sooner than if the --oversubscribe option was not set and allow higher system utilization, but application performance will likely suffer due to competition for resources.  This option applies to step allocations.
-S, --core-spec=<num> Count of specialized cores per node reserved by the job for system operations and not used by the application. The application will not use these cores, but will be charged for their allocation. Default value is dependent upon the node's configured CoreSpecCount value.  If a value of zero is designated and the Slurm configuration option AllowSpecResourcesUsage is enabled, the job will be allowed to override CoreSpecCount and use the specialized resources on nodes it is allocated.  This option can not be used with the --thread-spec option. This option applies to job allocations.
--signal=[R:]<sig_num>[@<sig_time>] When a job is within sig_time seconds of its end time, send it the signal sig_num.  Due to the resolution of event handling by Slurm, the signal may be sent up to 60 seconds earlier than specified. sig_num may either be a signal number or name (e.g. "10" or "USR1").  sig_time must have an integer value between 0 and 65535. By default, no signal is sent before the job's end time.  If a sig_num is specified without any sig_time, the default time will be 60 seconds. This option applies to job allocations.  Use the "R:" option to allow this job to overlap with a reservation with MaxStartDelay set.  To have the signal sent at preemption time see the preempt_send_user_signal SlurmctldParameter.
--slurmd-debug=<level> Specify a debug level for slurmd(8). The level may be specified either an integer value between 0 [quiet, only errors are displayed] and 4 [verbose operation] or the SlurmdDebug tags.
quiet     Log nothing
fatal     Log only fatal errors
error     Log only errors
info      Log errors and general informational messages
verbose   Log errors and verbose informational messages
The slurmd debug information is copied onto the stderr of the job. By default only errors are displayed. This option applies to job and step allocations.
--sockets-per-node=<sockets> Restrict node selection to nodes with at least the specified number of sockets.  See additional information under -B option above when task/affinity plugin is enabled. This option applies to job allocations.
--spread-job Spread the job allocation over as many nodes as possible and attempt to evenly distribute tasks across the allocated nodes. This option disables the topology/tree plugin.  This option applies to job allocations.
--switches=<count>[@<max-time>] When a tree topology is used, this defines the maximum count of switches desired for the job allocation and optionally the maximum time to wait for that number of switches. If Slurm finds an allocation containing more switches than the count specified, the job remains pending until it either finds an allocation with desired switch count or the time limit expires.  It there is no switch count limit, there is no delay in starting the job. Acceptable time formats include "minutes", "minutes:seconds", "hours:minutes:seconds", "days-hours", "days-hours:minutes" and "days-hours:minutes:seconds".  The job's maximum time delay may be limited by the system administrator using the SchedulerParameters configuration parameter with the max_switch_wait parameter option. On a dragonfly network the only switch count supported is 1 since communication performance will be highest when a job is allocate resources on one leaf switch or more than 2 leaf switches.  The default max-time is the max_switch_wait SchedulerParameters. This option applies to job allocations.
-T, --threads=<nthreads> Allows limiting the number of concurrent threads used to send the job request from the srun process to the slurmd processes on the allocated nodes. Default is to use one thread per allocated node up to a maximum of 60 concurrent threads. Specifying this option limits the number of concurrent threads to nthreads (less than or equal to 60).  This should only be used to set a low thread count for testing on very small memory computers. This option applies to job allocations.
A time limit of zero requests that no time limit be imposed. Acceptable time formats include "minutes", "minutes:seconds", "hours:minutes:seconds", "days-hours", "days-hours:minutes" and "days-hours:minutes:seconds". This option applies to job and step allocations.
--task-epilog=<executable> The slurmstepd daemon will run executable just after each task terminates. This will be executed before any TaskEpilog parameter in slurm.conf is executed. This is meant to be a very short-lived program. If it fails to terminate within a few seconds, it will be killed along with any descendant processes. This option applies to step allocations.
--task-prolog=<executable> The slurmstepd daemon will run executable just before launching each task. This will be executed after any TaskProlog parameter in slurm.conf is executed.  Besides the normal environment variables, this has SLURM_TASK_PID available to identify the process ID of the task being started.  Standard output from this program of the form "export NAME=value" will be used to set environment variables for the task being spawned. This option applies to step allocations.
--test-only Returns an estimate of when a job would be scheduled to run given the current job queue and all the other srun arguments specifying the job.  This limits srun's behavior to just return information; no job is actually submitted.  The program will be executed directly by the slurmd daemon. This option applies to job allocations.
--thread-spec=<num> Count of specialized threads per node reserved by the job for system operations and not used by the application. The application will not use these threads, but will be charged for their allocation.  This option can not be used with the --core-spec option. This option applies to job allocations.
--threads-per-core=<threads> Restrict node selection to nodes with at least the specified number of threads per core. In task layout, use the specified maximum number of threads per core. Implies --cpu-bind=threads. NOTE: "Threads" refers to the number of processing units on each core rather than the number of application tasks to be launched per core. See additional information under -B option above when task/affinity plugin is enabled. This option applies to job and step allocations.
--time-min=<time> Set a minimum time limit on the job allocation.  If specified, the job may have its --time limit lowered to a value no lower than --time-min if doing so permits the job to begin execution earlier than otherwise possible.  The job's time limit will not be changed after the job is allocated resources.  This is performed by a backfill scheduling algorithm to allocate resources otherwise reserved for higher priority jobs.  Acceptable time formats include "minutes", "minutes:seconds", "hours:minutes:seconds", "days-hours", "days-hours:minutes" and "days-hours:minutes:seconds". This option applies to job allocations.
--tmp=<size[units]> Specify a minimum amount of temporary disk space per node. Default units are megabytes.  Different units can be specified using the suffix [K|M|G|T].  This option applies to job allocations.
-u, --unbuffered By default the connection between slurmstepd and the user launched application is over a pipe. The stdio output written by the application is buffered by the glibc until it is flushed or the output is set as unbuffered.  See setbuf(3). If this option is specified the tasks are executed with a pseudo terminal so that the application output is unbuffered. This option applies to step allocations.
--uid=<user> Attempt to submit and/or run a job as user instead of the invoking user id. The invoking user's credentials will be used to check access permissions for the target partition. User root may use this option to run jobs as a normal user in a RootOnly partition for example. If run as root, srun will drop its permissions to the uid specified after node allocation is successful. user may be the user name or numerical user ID. This option applies to job and step allocations.
-v, --verbose Increase the verbosity of srun's informational messages.  Multiple -v's will further increase srun's verbosity.  By default only errors will be displayed. This option applies to job and step allocations.
-W, --wait=<seconds> Specify how long to wait after the first task terminates before terminating all remaining tasks. A value of 0 indicates an unlimited wait (a warning will be issued after 60 seconds). The default value is set by the WaitTime parameter in the slurm configuration file (see slurm.conf(5)). This option can be useful to ensure that a job is terminated in a timely fashion in the event that one or more tasks terminate prematurely.  Note: The -K, --kill-on-bad-exit option takes precedence over -W, --wait to terminate the job immediately if a task exits with a non-zero exit code. This option applies to job allocations.
-w, --nodelist=<host1,host2,... or filename> Request a specific list of hosts.  The job will contain all of these hosts and possibly additional hosts as needed to satisfy resource requirements.  The list may be specified as a comma-separated list of hosts, a range of hosts (host[1-5,7,...] for example), or a filename.  The host list will be assumed to be a filename if it contains a "/" character.  If you specify a minimum node or processor count larger than can be satisfied by the supplied host list, additional resources will be allocated on other nodes as needed.  Rather than repeating a host name multiple times, an asterisk and a repetition count may be appended to a host name. For example "host1,host1" and "host1*2" are equivalent. If the number of tasks is given and a list of requested nodes is also given, the number of nodes used from that list will be reduced to match that of the number of tasks if the number of nodes in the list is greater than the number of tasks. This option applies to job and step allocations.
--wckey=<wckey> Specify wckey to be used with job.  If TrackWCKey=no (default) in the slurm.conf this value is ignored. This option applies to job allocations.
-X, --disable-status Disable the display of task status when srun receives a single SIGINT (Ctrl-C). Instead immediately forward the SIGINT to the running job.  Without this option a second Ctrl-C in one second is required to forcibly terminate the job and srun will immediately exit. May also be set via the environment variable SLURM_DISABLE_STATUS. This option applies to job allocations.
-x, --exclude=<host1,host2,... or filename> Request that a specific list of hosts not be included in the resources allocated to this job. The host list will be assumed to be a filename if it contains a "/" character. This option applies to job and step allocations.
--x11[=<all|first|last>] Sets up X11 forwarding on all, first or last node(s) of the allocation. This option is only enabled if Slurm was compiled with X11 support and PrologFlags=x11 is defined in the slurm.conf. Default is all.
-Z, --no-allocate Run the specified tasks on a set of nodes without creating a Slurm "job" in the Slurm queue structure, bypassing the normal resource allocation step.  The list of nodes must be specified with the -w, --nodelist option.  This is a privileged option only available for the users "SlurmUser" and "root". This option applies to job allocations.
srun will submit the job request to the slurm job controller, then initiate all processes on the remote nodes. If the request cannot be met immediately, srun will block until the resources are free to run the job. If the -I (--immediate) option is specified srun will terminate if resources are not immediately available.
When initiating remote processes srun will propagate the current working directory, unless --chdir=<path> is specified, in which case path will become the working directory for the remote processes.
The -n, -c, and -N options control how CPUs  and nodes will be allocated to the job. When specifying only the number of processes to run with -n, a default of one CPU per process is allocated. By specifying the number of CPUs required per task (-c), more than one CPU may be allocated per process. If the number of nodes is specified with -N, srun will attempt to allocate at least the number of nodes specified.
Combinations of the above three options may be used to change how processes are distributed across nodes and cpus. For instance, by specifying both the number of processes and number of nodes on which to run, the number of processes per node is implied. However, if the number of CPUs per process is more important then number of processes (-n) and the number of CPUs per process (-c) should be specified.
srun will refuse to  allocate more than one process per CPU unless --overcommit (-O) is also specified.
srun will attempt to meet the above specifications "at a minimum." That is, if 16 nodes are requested for 32 processes, and some nodes do not have 2 CPUs, the allocation of nodes will be increased in order to meet the demand for CPUs. In other words, a minimum of 16 nodes are being requested. However, if 16 nodes are requested for 15 processes, srun will consider this an error, as 15 processes cannot run across 16 nodes.
IO Redirection
By default, stdout and stderr will be redirected from all tasks to the stdout and stderr of srun, and stdin will be redirected from the standard input of srun to all remote tasks.  If stdin is only to be read by a subset of the spawned tasks, specifying a file to read from rather than forwarding stdin from the srun command may be preferable as it avoids moving and storing data that will never be read.
For OS X, the poll() function does not support stdin, so input from a terminal is not possible.
This behavior may be changed with the --output, --error, and --input (-o, -e, -i) options. Valid format specifications for these options are
all       stdout stderr is redirected from all tasks to srun.  stdin is broadcast to all remote tasks.  (This is the default behavior)
none      stdout and stderr is not received from any task.  stdin is not sent to any task (stdin is closed).
taskid    stdout and/or stderr are redirected from only the task with relative id equal to taskid, where 0 <= taskid <= ntasks, where ntasks is the total number of tasks in the current job step. stdin is redirected from the stdin of srun to this same task. This file will be written on the node executing the task.
filename  srun will redirect stdout and/or stderr to the named file from all tasks.  stdin will be redirected from the named file and broadcast to all tasks in the job.  filename refers to a path on the host that runs srun.  Depending on the cluster's file system layout, this may result in the output appearing in different places depending on whether the job is run in batch mode.
filename pattern srun allows for a filename pattern to be used to generate the named IO file described above. The following list of format specifiers may be used in the format string to generate a filename that will be unique to a given jobid, stepid, node, or task. In each case, the appropriate number of files are opened and associated with the corresponding tasks. Note that any format string containing %t, %n, and/or %N will be written on the node executing the task rather than the node where srun executes, these format specifiers are not supported on a BGQ system.
Executing srun sends a remote procedure call to slurmctld. If enough calls from srun or other Slurm client commands that send remote procedure calls to the slurmctld daemon come in at once, it can result in a degradation of performance of the slurmctld daemon, possibly resulting in a denial of service.
Do not run srun or other Slurm client commands that send remote procedure calls to slurmctld from loops in shell scripts or other programs. Ensure that programs limit calls to srun to the minimum necessary for the information you are trying to gather.
Some srun options may be set via environment variables.  These environment variables, along with their corresponding options, are listed below.  Note: Command line options will always override these settings.
PMI_FANOUT            This is used exclusively with PMI (MPICH2 and MVAPICH2) and controls the fanout of data communications. The srun command sends messages to application programs (via the PMI library) and those applications may be called upon to forward that data to up to this number of additional tasks. Higher values offload work from the srun command to the applications and likely increase the vulnerability to failures.  The default value is 32.
PMI_FANOUT_OFF_HOST   This is used exclusively with PMI (MPICH2 and MVAPICH2) and controls the fanout of data communications.  The srun command sends messages to application programs (via the PMI library) and those applications may be called upon to forward that data to additional tasks. By default, srun sends one message per host and one task on that host forwards the data to other tasks on that host up to PMI_FANOUT.  If PMI_FANOUT_OFF_HOST is defined, the user task may be required to forward the data to tasks on other hosts.  Setting PMI_FANOUT_OFF_HOST may increase performance. Since more work is performed by the PMI library loaded by the user application, failures also can be more common and more difficult to diagnose.
PMI_TIME              This is used exclusively with PMI (MPICH2 and MVAPICH2) and controls how much the communications from the tasks to the srun are spread out in time in order to avoid overwhelming the srun command with work. The default value is 500 (microseconds) per task. On relatively slow processors or systems with very large processor counts (and large PMI data sets), higher values may be required.
SLURM_ACCOUNT         Same as -A, --account
SLURM_ACCTG_FREQ      Same as --acctg-freq
SLURM_BCAST           Same as --bcast
SLURM_BURST_BUFFER    Same as --bb
SLURM_CLUSTERS        Same as -M, --clusters
SLURM_COMPRESS        Same as --compress
SLURM_CONSTRAINT      Same as -C, --constraint
SLURM_CORE_SPEC       Same as --core-spec
SLURM_CPU_BIND        Same as --cpu-bind
SLURM_CPU_FREQ_REQ    Same as --cpu-freq.
SLURM_CPUS_PER_GPU    Same as --cpus-per-gpu
SLURM_CPUS_PER_TASK   Same as -c, --cpus-per-task
SLURM_DEBUG           Same as -v, --verbose
SLURM_DELAY_BOOT      Same as --delay-boot
SLURMD_DEBUG          Same as -d, --slurmd-debug
SLURM_DEPENDENCY      Same as -P, --dependency=<jobid>
SLURM_DISABLE_STATUS  Same as -X, --disable-status
SLURM_DIST_PLANESIZE  Plane distribution size. Only used if --distribution=plane, without =<size>, is set.
SLURM_DISTRIBUTION    Same as -m, --distribution
SLURM_EPILOG          Same as --epilog
SLURM_EXCLUSIVE       Same as --exclusive