We've run into the same problem ("problem with bind(): Invalid
argument") using LAM 7.0 but setting the $LAM_MPI_SESSION_PREFIX
environment variable didn't seem to affect the path used. Is there
something else that needs to be done?
Is there a projected release date for 7.0.1?
Thanks,
Steve
> We iterated off-list a little to solve this problem. Short version:
> -------------- 1. There is a problem with LAM 6.5.x and 7.0 if you try
> to use a unix socket with a really long pathname. It rarely/never
> happens in 6.5.x, but can happen in 7.0 in environments where, for
> example, $TMPDIR has a very long value. 2. There are workarounds for
> both versions: - in 6.5.x, set $LAM_MPI_SOCKET_SUFFIX to something
> shorter. - in 7.0, set $LAM_MPI_SESSION_PREFIX to something shorter.
> This will take precedence over $TMPDIR. 6.5.x is unlikely to be fixed
> (since it is officially retired). Fixes for 7.0 have been committed to
> CVS. Since there is a workaround, and since this bug affects so few
> people, we do not plan to release 7.0.1 because of it. Future versions
> of LAM/MPI will include this fix.
--
Steven M. Wilson, Systems and Network Manager
Markey Center for Structural Biology
Purdue University
(765) 496-1946
|
