Hp XC System 2.x Software Manual de usuario Pagina 31

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 154
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 30
If you encounter a modulefile conflict when loading a modulefil e, you must unload the
conflicting modulefile before y ou load the new modulefile. Refer to Section 2.2.8 for f urther
information about modulefile conflicts.
2.2.6.1 Loading a M odulefile for the Current Session
Yo u can load a modulefile for your current login session as needed. To do this, issue
the module load command as shown in the following example, which illustrates the
TotalView modulefile being loaded:
$ module load totalview
Loading a modulefile in this manner affects your environment for the curren t session only.
2.2.6.2 Automatically Loading a Modulefile at Login
If you frequently use o ne or more modulefiles that are not lo aded when you log in to the
system, you can set up your environment to automatically load those mod ulefiles for you. A
method for d oing this is to modify your shell startup script to incl ude instructions to load the
modulefile automatically.
For exam ple, if you wanted to automatically load the TotalView modulefile wh en you log in,
edit you r shell startup script to includ e 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
fi
From now on, whenever you log in, the TotalView modulefile is automatically loaded in your
environment.
2.2.7 Unloading a M odulefile
In certain cases, you may find it necessary to unload a particular modulefile before you can load
another mod ulefile in to y our environment to avoid modulefile conflicts. Refer t o Section 2.2.8
for information ab out modulefile conflicts.
You can unload a modulefile by using th e module unload command, as shown in the
following example:
$ module unload ifort/8.0
Unloading a modulefile th at is loaded b y default makes it inactive for the current session only
it will be reloaded the next time you log in.
2.2.8 Modulefile Conflicts
Some modulefiles sh oul d not be loaded while certain other modulefi les are curren tly loaded.
This is especially true of m odulefiles for different versions of the same softw are. For example,
the Intel C/C++ Version 8.0 compiler modulefile should not be loade d while the
Intel C/C++ Version 8.1 compiler modulefile is loaded . A modulefile conflict occurs
in this situation.
The system will display an error message when you att emp t 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’
Using the System 2-5
Vista de pagina 30
1 2 ... 26 27 28 29 30 31 32 33 34 35 36 ... 153 154

Comentarios a estos manuales

Sin comentarios