C H A P T E R 3 |
Before You Begin |
This chapter provides miscellaneous information about the runtime environment that you should know before you begin to use it. It contains the following sections:
If your program uses Sun HPC ClusterTools components, compile and link it on a cluster that contains the Sun HPC ClusterTools software.
It is strongly suggested that you use the Sun HPC ClusterTools 8.1 wrapper compilers to compile applications. These wrapper compilers add the appropriate compiler and linker flags to the command line and call the underlying compiler and linker for you. Wrapper compilers are available for C, C++, Fortran 77, and Fortran 90.
For more information about compiling MPI applications, see the “Compiling MPI Applications” FAQ at:
http://www.open-mpi.org/faq/?category=mpi-apps
Sun HPC ClusterTools commands typically reside in the following directories:
You can run the Sun HPC ClusterTools software directly from the directory in which yourClusterTools commands are installed, or you may add the directory to your PATH or set the PATH environment variable.
The man pages for Sun HPC ClusterTools commands reside in the /opt/SUNWhpc/man directory.
The Sun HPC ClusterTools files typically reside in /opt/SUNWhpc/HPC8.1.
To Set Up Your Path for the Solaris OS and the Sun Studio Compiled Linux Version |
For example, if you installed the Sun HPC ClusterTools 8.1 software for the Solaris OS in the default location of /opt/SUNWhpc/HPC8.1/sun/bin, you would add this location to your PATH as shown in the following example:
The setenv command prefixes the PATH on both the local and remote hosts with /opt/SUNWhpc/HPC8.1/sun/bin.
For example, if you installed the GNU compiled version of the Sun HPC ClusterTools 8.1 software for Linux in the default location of /opt/SUNWhpc/HPC8.1/gnu/bin, you would add this location to your PATH as shown in the following example:
The setenv command prefixes the PATH on both the local and remote hosts with /opt/SUNWhpc/HPC8.1/gnu/bin.
Core files are produced as they normally are in the Solaris environment. However, if more than one process dumps core in a multiprocess program, the resulting core file may be overwritten in the same directory. Use coreadm(1M) to control the naming and placement of core files.
To disable the core dump, use the limit(1) command. You can use the following command in the C shell:
If you are using ssh to connect to your remote nodes, you must set up your ~/.ssh/known_hosts file to contain the remote nodes’ host key, especially if you try to run on a cluster with many nodes for the first time.
Setting up the known_hosts file avoids having to respond to the following prompts when running mpirun to the remote nodes:
Copyright © 2008 Sun Microsystems, Inc. All Rights Reserved.