This page provides release notes for LAM targeted at LAM users. The
bulk of the release notes for LAM/MPI 7.0.5 are in the
Installation Guide and
User's Guide. Both
documents are also included in the doc/ directory of
every LAM/MPI tarball.
On systems with case-insensitive filesystems (such as Mac OS X with
HFS+, or Linux with NTFS), the mpicc and mpiCC commands
will both refer to the same executable. This obviously makes
distinguishing between the mpicc and mpiCC wrapper
compilers impossible. LAM will attempt to determine if you are
building on a case-insensitive filesystem. If you are, the C++
wrapper compiler will be called mpic++. Otherwise, the C++
compiler will be called mpiCC (although mpic++ will also
be available).
The LAM per-session directory may not work properly when hosted in an
NFS directory, and may cause problems when running MPI programs and/or
supplementary LAM run-time environment commands. If using a local
filesystem is not possible (e.g., on diskless workstations), the use
of tmpfs or tinyfs is recommended. LAM's session
directory will not grow large; it contains a small amount of meta data
as well as known endpoints for Unix sockets to allow LAM/MPI programs
to contact the local LAM run-time environment daemon.
AFS has some peculiarities, especially with file permissions when
using rsh/ssh.
Many sites tend to install the AFS rsh replacement that
passes tokens to the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default rsh.
Similarly, m the remote machine as the default |
