Actions

Difference between revisions of "Purging all modules"

From ALICE Documentation

(Created page with "==== Purging all modules ==== In order to unload all modules at once, and hence be sure to start in a clean state, you can use: $ module purge This is always safe: the cl...")
 
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
====  Purging all modules  ====
 
====  Purging all modules  ====
 
In order to unload all modules at once, and hence be sure to start in a clean state, you can use:  
 
In order to unload all modules at once, and hence be sure to start in a clean state, you can use:  
   $ module purge
+
   $ '''module purge'''
 
This is always safe: the cluster module (the module that specifies which cluster jobs will get submitted to) will not be unloaded (because it’s a so-called “sticky” module).
 
This is always safe: the cluster module (the module that specifies which cluster jobs will get submitted to) will not be unloaded (because it’s a so-called “sticky” module).
  $ module load example
 
rather than
 
  $ module load example/1.2.3
 
Everything works fine, up to the point where a new version of example is installed, 4.5.6. From then on, the user’s load command will load the latter version, rather than the intended one, which may lead to unexpected problems. See for example section 8.8.
 
 
Consider the following example modules:
 
  $ module avail example/
 
  example/1.2.3
 
  example/4.5.6
 
Let’s now generate a version conflict with the example module, and see what happens.
 
  $ module av example/
 
  example/1.2.3
 
  example/4.5.6
 
  $ module load example/1.2.3 example/4.5.6 Lmod has detected the following error: A different version of the ’example’ module is already loaded (see output of ’ml’). $ module swap example/4.5.6
 
 
Note: A module swap command combines the appropriate module unload and module load commands.
 

Latest revision as of 14:29, 17 April 2020

Purging all modules

In order to unload all modules at once, and hence be sure to start in a clean state, you can use:

 $ module purge

This is always safe: the cluster module (the module that specifies which cluster jobs will get submitted to) will not be unloaded (because it’s a so-called “sticky” module).