...
No Format |
---|
$ module load git; echo return_code=$?
load git 2.20.1 (git_DIR, GIT_VERSION, PATH)
return_code=0
$ module load foo; echo return_code=$?
Lmod has detected the following error: The following module(s) are unknown: "foo"
Please check the spelling or version number. Also try "module spider ..."
It is also possible your cache file is out-of-date; it may help to try:
$ module --ignore-cache load "foo"
Also make sure that all modulefiles written in TCL start with the string #%Module
return_code=1 |
...
No Format |
---|
$ module load git load git 2.20.1 (git_DIR, GIT_VERSION, PATH) usxa@at1-11: ~ [2020-03-18 16:03:57 UTC] [0] $ module load git/new unload git 2.20.1 (git_DIR, GIT_VERSION, PATH) load git 2.25.1 (git_DIR, GIT_VERSION, PATH) The following have been reloaded with a version change: 1) git/2.20.1 => git/2.25.1 |
...
No Format |
---|
$ module avail git -------------------------------------------------------------------------------------- Global Aliases --------------------------------------------------------------------------------------- pa -> prgenv/amd pe -> prgenv/expert pg -> prgenv/gnu pi -> prgenv/intel pp -> prgenv/pgi --------------------------------------------------------------------------- /usr/local/apps/modulefiles/lmod/core --------------------------------------------------------------------------- git/2.20.1 (D) git/2.25.1 (new) Where: Aliases: Aliases exist: foo/1.2.3 (1.2) means that "module load foo/1.2" will load foo/1.2.3 D: Default Module Use "module spider" to find all possible modules and extensions. Use "module keyword key1 key2 ..." to search for all possible modules matching any of the "keys". $ module load git/2 load git 2.20.1 (git_DIR, GIT_VERSION, PATH) $ module load git/2.25 unload git 2.20.1 (git_DIR, GIT_VERSION, PATH) load git 2.25.1 (git_DIR, GIT_VERSION, PATH) The following have been reloaded with a version change: 1) git/2.20.1 => git/2.25.1 |
...
If two modules cannot be loaded at the same time due to a conflict, the old one will be swapped out and the new one will be loaded automatically.
No Format |
---|
usxa@at1-11: ~ [2020-03-18 16:06:12 UTC] [0] $ module load proj4 load proj4 5.2.0 (PROJ4_DIR, PROJ4_VERSION, PROJ4_INCLUDE, PROJ4_LIB, PATH, MANPATH) usxa@at1-11: ~ [2020-03-18 16:06:29 UTC] [0] $ module load proj load proj 6.1.1 (PROJ_DIR, PROJ_VERSION, PROJ_INCLUDE, PROJ_LIB, PATH, MANPATH) Lmod is automatically replacing "proj4/5.2.0" with "proj/6.1.1". unload proj4 5.2.0 (PROJ4_DIR, PROJ4_VERSION, PROJ4_INCLUDE, PROJ4_LIB, PATH, MANPATH) unload proj 6.1.1 (PROJ_DIR, PROJ_VERSION, PROJ_INCLUDE, PROJ_LIB, PATH, MANPATH) load proj 6.1.1 (PROJ_DIR, PROJ_VERSION, PROJ_INCLUDE, PROJ_LIB, PATH, MANPATH) |
Native flavour support
You may feel that some packages or versions are missing when running the classic module avail. Lmod knows about those packages that are flavoured for different environments (compilers or MPI), and will only show as available to load those that have been installed for the currently loaded environment. This guarantees that when loading a module the right flavour of the tool or library will be used, avoiding incompatibilities.
...