On Sep 20, 2005, at 10:47 PM, John L Bartelt wrote:
> I have a cluster of thin clients using ltsp that I want to use as a
> parallel
> computing array with lam-mpi. I can do password free ssh to the
> clients if
> /tmp is not writable. Unfortunately lam processes need to write to /
> tmp. If
> I make /tmp writable, ssh won't tolerate it. Is there a solution or
> workaround?
/tmp should always be world readable (with the +t bit set, of
course). Otherwise, it's not very, um, temporary. I would imagine
that LAM is only one of many programs that will cause problems if /
tmp isn't writable by the user. I think you have ssh improperly
configured or your permissions set incorrectly in /tmp if ssh is
complaining. You might want to talk to the ssh people about the
problem.
You can set the directory LAM uses for it's temporary directory by
setting the TMPDIR environment variable on each node as part of the
login script.
Hope this helps,
Brian
--
Brian Barrett
LAM/MPI developer and all around nice guy
Have a LAM/MPI day: http://www.lam-mpi.org/
|
