Module Environments

Each modulefile contains the information needed to configure the shell for an application. Once the Modules package is initialized, the environment can be modified on a per-module basis using the module command which interprets modulefiles. Typically modulefiles instruct the module command to alter or set shell environment variables such as PATH, MANPATH, etc. modulefiles may be shared by many users on a system and users may have their own collection to supplement or replace the shared modulefiles.

Modules can be loaded and unloaded dynamically and atomically, in an clean fashion. All popular shells are supported, including bash, ksh, zsh, sh, csh, tcsh, as well as some scripting languages such as perl and python.

Modules are useful in managing different versions of applications. Modules can also be bundled into metamodules that will load an entire suite of different applications.

Here is an example of loading a module on the Shamu cluster.
[abc123@login01 ~]$ module load shared sge
[abc123@login01 ~]$ module list 
Currently Loaded Modulefiles:
 1) shared 2) slurm/18.08.4 3) sge/2011.11p1

You can also autoload modules if you do not want to load them each time you log into Shamu.
[abc123@login01 ~]$ module initadd shared sge

The above command will add the "shared" module and the "sge" module to your login scripts.

-- AdminUser - 05 Oct 2016
Topic revision: r2 - 03 Jun 2019, AdminUser
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding UTSA Research Support Group? Send feedback