"sbatch --begin=uts458389988 my.script").

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

    get purged before their trigger can be processed (e.g. MinJobAge=1).

    RLIMIT_STACK.

    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.

Fixed issue where if the slurmdbd was down past the MinJobAge and the start of the job hadn't been sent yet to throw it on the queue to be sent when the slurmdbd comes back up.

    that of the slurmctld daemon: the same directory used for log files,
    SlurmdLogFile (if specified with an absolute pathname) otherwise the
    directory used to save state, SlurmdSpoolDir.

    affinity is enabled, keep track of the individual CPUs allocated to jobs
    rather than just the count of CPUs allocated (which could overcommit
    specific CPUs for running jobs).

Fix for handling correctly jobs that resize, and also reporting correct stats on a job after it finishes.

    preempted jobs at the time slurmctld restarts that can result in over-
    subscribing resources.

    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.

    scontrol show config command output. The use of SlurmDBD is still strongly
    recommended as SLURM will have limited database functionality or protection
    otherwise.

    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.

    within an existing job allocation.

    message upon job begin.