From bbd9052bd96ff507a14f9b6e0e90e7680d8516b7 Mon Sep 17 00:00:00 2001 From: Roman Sliva <roman.sliva@vsb.cz> Date: Tue, 18 Jul 2023 09:05:02 +0200 Subject: [PATCH] Update slurm-job-submission-and-execution.md --- .../general/slurm-job-submission-and-execution.md | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/docs.it4i/general/slurm-job-submission-and-execution.md b/docs.it4i/general/slurm-job-submission-and-execution.md index 55b00ffc3..8ee7741d3 100644 --- a/docs.it4i/general/slurm-job-submission-and-execution.md +++ b/docs.it4i/general/slurm-job-submission-and-execution.md @@ -10,12 +10,6 @@ A `man` page exists for all Slurm commands, as well as `--help` command option, which provides a brief summary of options. Slurm [documentation][c] and [man pages][d] are also available online. -To view all of the Slurm's environment variables, use the command: - -```shell -set | grep ^SLURM -``` - ### Quick Overview of Common Commands | Command | Explanation | @@ -130,6 +124,15 @@ Notice that Slurm spread our job across 2 different nodes; by default, Slurm sel * Beginning with 22.05, `srun` will not inherit the `--cpus-per-task` value requested by `salloc` or `sbatch`. It must be requested again with the call to `srun` or set with the `SRUN_CPUS_PER_TASK` environment variable if desired for the task(s). +#### Job environment_variables + +Slurm exposes useful information about job to job main process (usually shell) via environment variables. +To view all of the Slurm's environment variables, use the command: + +```shell +set | grep ^SLURM +``` + #### Common Job Workflow !!! Note -- GitLab