Chapter 14 Managing Modulefiles

This chapter describes how to load, unload, and examine modulefiles.

Modulefiles provide a mechanism for accessing software commands and tools, particularly for third-party software. The HP XC System Software does not use modules for system-level manipulation.

A modulefile contains the information that alters or sets shell environment variables, such as PATH and MANPATH. Some modulefiles are provided with the HP XC System Software and are available for you to load. A modulefile must be loaded before it changes the user's environment.

See the HP XC System Software User's Guide for information on creating modulefiles and loading default modulefiles.

The module command features keywords that enable you to load, unload, and list modules, as described here.

Use the load keyword to load a module:
# module load package-name
Use the list keyword to list all loaded modules:
Be sure to unload a module before loading another to help avoid module versioning conflicts. See the HP XC System Software User's Guide for additional information.
# module list
Use the avail keyword to list all loaded or unloaded modules:
# module avail
Use the unload keyword to unload a module:
# module unload package-name




	Notes: Installing a package in a nondefault location means that you must update the corresponding modulefile; you might need to edit the `PATH` and `MANPATH` environment variables. Other changes are based on the software package and its dependencies. If you have installed a variant of the package, you might need to create a parallel modulefile specifically for the variant. For example, you might have a standard application that you need to keep separate from a beta version of the same application; in this case, you would set up a parallel modulefile and adjust it accordingly.

Chapter 14 Managing Modulefiles

Technical documentation

» Table of Contents

» Glossary

» Index