HP XC System Software Administration Guide Version 3.2

Use either of the following methods for setting up NIS on your HP XC system:
• Set all the nodes as NIS clients. Both the master and slave NIS server are external to the HP
XC system.
• Set the head node as a NIS slave (secondary) server. The NIS master server is external to the
HP XC system. Nodes within the HP XC system use the internal server for NIS information.
HP recommends this configuration for larger systems using NIS.
1.9 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 is a shell function that is defined when users log into the system. It is not
found in the path; you can ensure this function exists by running the following command under
the Bourne, Korn, or bash shells:
$ typeset -f module
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:
# module list
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.
• 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
See the HP XC System Software User's Guide for more information about modulefiles.
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.
1.10 Security
This section describes measures for maintaining the security of the HP XC system.
1.9 Modulefiles 43