Running jobs/fr: Difference between revisions

Jump to navigation Jump to search
Updating to match new version of source page
(Updating to match new version of source page)
(Updating to match new version of source page)
Line 386: Line 386:


==== Jobs inherit environment variables ====
==== Jobs inherit environment variables ====
By default a job will inherit the environment variables of the shell where the job was submitted (see the <code>--export</code> option on the [https://slurm.schedmd.com/sbatch.html sbatch man page] for more details about how to control how environment variables are inherited). Since the <code>module</code> commands operate on environment variables, changes made by using these commands will propagate to any jobs submitted from that shell and thus could affect the job's ability to load modules if there are missing prerequisites.
By default a job will inherit the environment variables of the shell where the job was submitted. When using the [[Using modules|module]] command to make various software packages available for use the command modifies and sets environment variables. Changes made by using these commands will propagate to any jobs submitted from that shell after these changes have been made and thus could affect the job's ability to load modules if there are missing prerequisites. It is best to include the line <code>module purge</code> in your job script before loading all the required modules to ensure a consistent state for each job submission and avoid changes made in your shell affecting your jobs.


==État des tâches et priorité==
==État des tâches et priorité==
35,279

edits

Navigation menu