From 0dd9a073cdf5b4014eb999c67bc10e3a1de6e759 Mon Sep 17 00:00:00 2001 From: TopRichard <121792457+TopRichard@users.noreply.github.com> Date: Thu, 17 Oct 2024 13:37:47 +0200 Subject: [PATCH] Update docs/using_eessi/setting_up_environment.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Thomas Röblitz --- docs/using_eessi/setting_up_environment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/using_eessi/setting_up_environment.md b/docs/using_eessi/setting_up_environment.md index ef3a5d053..c770f53a1 100644 --- a/docs/using_eessi/setting_up_environment.md +++ b/docs/using_eessi/setting_up_environment.md @@ -19,7 +19,7 @@ There are a few different scenarios where you may want to set up the EESSI envir :clap: Your environment is now set up, you are ready to start running software provided by EESSI! -2. You are using an older version of Lmod or any other tool utilizing `MODULEPATH` (Tmod, etc.) +2. You are using an Lmod with a version older than 8.6 or any other tool utilizing `MODULEPATH` (Tmod, etc.) You should unset MODULEPATH to prevent Lmod from attempting to build a cache for your module tree (as this can be very slow if you have a lot of modules). Again, unsetting the MODULEPATH should be considered as a good idea in general so you do not mix local and EESSI