HP XC System Software User's Guide Version 3.2

For example, if you wanted to automatically load the TotalView modulefile when you log in,

edit your shell startup script to include the following instructions. This example uses bash as

the login shell. Edit the ~/.bashrc file as follows:

# if the 'module' command is defined, $MODULESHOME

# will be set

if [ -n "$MODULESHOME" ]; then

module load totalview

From now on, whenever you log in, the TotalView modulefile is automatically loaded in your

environment.

3.7 Unloading a Modulefile

In certain cases, you may find it necessary to unload a particular modulefile before you can load

another modulefile in to your environment, to avoid modulefile conflicts. See “Modulefile

Conflicts” for information about modulefile conflicts.

You can unload a modulefile by using the module unload command, as shown in the following

example:

$ module unload ifort/8.0

Unloading a modulefile that is loaded by default makes it inactive for the current session only

— it will be reloaded the next time you log in.

3.8 Viewing Modulefile-Specific Help

You can view help information for any of the modulefiles on the HP XC system. For example,

to access modulefile-specific help information for TotalView, issue the module help command

as follows:

$ module help totalview

----------- Module Specific Help for 'totalview/default' -----------------

This loads the TotalView environment.

Version <default>

Modifies: MANPATH, PATH, TVDSVRLAUNCHCMD

NOTE: The term <default> is displayed whenever the modulefile originator does not use

version numbers to distinguish the modulefiles.

3.9 Modulefile Conflicts

Some modulefiles should not be loaded while certain other modulefiles are currently loaded.

This is especially true of modulefiles for different versions of the same software. For example,

the Intel C/C++ Version 8.0 compiler modulefile should not be loaded while the Intel

C/C++ Version 8.1 compiler modulefile is loaded. A modulefile conflict occurs in this

situation.

The system displays an error message when you attempt to load a modulefile that conflicts with

one or more currently loaded modulefiles. For example:

$ module load ifort/8.0

ifort/8.0(19):ERROR:150: Module 'ifort/8.0' conflicts with the

currently loaded module(s) 'ifort/8.1'

ifort/8.0(19):ERROR:102: Tcl command execution failed:

conflict ifort/8.1

3.7 Unloading a Modulefile 41