MHPCC
Riptide & US Maintenance - Wednesday, April 30th, 2014
15 April 2014
The MHPCC Riptide & US systems will be undergoing scheduled maintenance on Wednesday, April 30th, 2014 from 0800 (HST) - 1700 (HST).

Please plan accordingly.

Thank You,
MHPCC User Services
DREN Maintenance on Thursday, April 17th & 19th, 2014
02 April 2014
DREN Maintenance on on Thursday, April 17th, 2014 at 1300 GMT (0300 HST) & Saturday, April 19th, 2014 at 1300 GMT (0300 HST)

This may affect connectivity to MHPCC systems during the subject stated maintenance window.

Please plan accordingly.

Thank you,
MHPCC User Services
Holiday Notice - Friday, April 18th, 2014
03 March 2014
On Friday, April 18th, 2014 MHPCC will be operating on a holiday schedule. The center will be open and all technology services will be available, however MHPCC will be operating at reduced staffing levels.

If you require assistance, onsite staff will be available to respond to Severity 1 Help Desk calls at 808-879-5077, and if necessary, MHPCC will contact other technical staff if needed. If you anticipate requiring any special assistance on April 18th, please contact our User Services department or the CCAC by email or by telephone.


Home » Documentation
Printable versionPrintable version

Modules User Guide

Table Of Contents

Introduction
Module Commands
Initializing Modules Software
Types of Modules Available

Introduction

Modules provides an easy mechanism for dynamically updating a user's environment, especially the $PATH, $MANPATH, $NLSPATH, and $LD_LIBRARY_PATH environment variables to name a few. Each module contains the information needed to configure the shell for an application or library. To perform this in the current shell, the modules package uses the shell's eval 'command' mechanism for running a program that outputs shell commands and then executes them. There are some limitations and preferred ways for setting up the modules environment because of this implementation. Modulefiles may be shared by many users on a system and users may have their own collection to supplement or replace the existing shared modulefiles.

Module Commands

module help [modulefile...]

Print the usage of each sub-command. If an argument is given, print the Module specific help information for the modulefile.

module load modulefile [modulefile...]

Load modulefile into the shell environment.

module unload modulefile [modulefile...]

Remove modulefile from the shell environment.

module switch modulefile1 modulefile2

Switch loaded modulefile1 with modulefile2.

module display modulefile [modulefile...]

The display sub-command will list the full path of the modulefile and all (or most) of the environment changes the modulefile will make if loaded.

module list

List loaded modules.

module avail [path...]

List all available modulefiles in the current $MODULEPATH. All directories in the $MODULEPATH are recursively searched for files containing the modulefile magic cookie.

module use [-a|--append] directory [directory...]

Prepend directory to the $MODULEPATH environment variable. The "--append" flag will append the directory to $MODULEPATH.

module unuse directory [directory...]

Remove directory from the $MODULEPATH environment variable.

module update

Attempt to reload all loaded modulefiles. The environment will be reconfigured to match the saved ${HOME}/.modulesbeginenv and the modulefiles will be reloaded.

module clear

Force the Modules Package to believe that no modules are currently loaded.

module purge

Unload all loaded modulefiles.

Initializing Modules Software

The Modules environment should automatically set up in your environment when you log in. If for some reason it is not, you may do it manually by issuing the following command:

source /usr/share/Modules/init/

Where shell=sh, csh, tcsh, ksh or bash, depending on which shell is your login shell. This command may also be put in your .cshrs.pers or .profile.pers files.

Types of Modules Available

When a user enters the "module avail" command a list of all the modules currently available to the user for loading are displayed. This list is broken down into four categories: COTS, Unsupported, Modules and Devel.

COTS modules initialize access to vendor codes installed and maintained by MHPCC DSRC staff. Most of these codes are available to all users. A few of these packages are ITAR controlled, and can only be accessed after requesting to be added the UNIX group under which the code was built. There are sample scripts in the Sample Code Repository ($SAMPLES_HOME) that provide examples of how to run most of these codes on the system.

Unsupported modules initialize access to codes that have been installed and are maintained by individual users who are not part of the MHPCC DSRC staff. These codes are installed in an area provided to the owner to allow access to them by more than the owner of the code. However, access is usually, but not always, group controlled.

The modules in the Modules area are the modules that are part of a user's default login environment and are automatically loaded as part of the login process.

Devel modules initialize access to program development tools such as compilers, parallel programming libraries and program development libraries. You can find samples and descriptions of how to use the various compilers and libraries in the Sample Code Repository ($SAMPLES_HOME).

^ top