I realize from the FAQ and from past experience that an MPI application
must be compiled for a specific version of LAM. I am trying to plan how
we will make the transition from our old version (lam-6.6b2) to a new
version (e.g., lam-7.0.6). We release a new version of our application
every week or two, but the old versions hang around and continue to be used.
I recall from a previous upgrade a few years ago that we can continue to
use multiple versions of LAM as long as we set LAMHOME and PATH
appropriately. The problem is that this is not very selectable
dynamically. It used to require that we set those environment variables
in each user's startup scripts (.cshrc or related scripts), so that the
lamd's started by lamboot would be the correct ones.
Is the situation still as restrictive? For instance, if lamboot were to
start up lamd's on remote machines using an absolute path and
communicating LAMHOME directly, it would only require the environment to
be correct in the shell where the application startup script (the one
that calls lamboot) is executed.
I'm looking for an easier way to have our application select the LAM
version when the user starts it. Right now it seems that the startup
script will have to write a resource file (e.g., .lamrc) in the user's
home directory that his .cshrc file will source to set the environment
variables.
Any other ideas?
--
Dick Hadsell 914-259-6320 Fax: 914-259-6499
Reply-to: hadsell_at_[hidden]
Blue Sky Studios http://www.blueskystudios.com
44 South Broadway, White Plains, NY 10601
|
