On Apr 16, 2009, at 11:29 AM, Francesco Pietra wrote:
francesco@tya64:~$ ssh 192.168.1.33 env | sort
HOME=/home/francesco
LANG=en_US.UTF-8
LOGNAME=francesco
MAIL=/var/mail/francesco
PATH=/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games
PWD=/home/francesco
SHELL=/bin/bash
SHLVL=1
SSH_CLIENT=192.168.1.37 33941 22
SSH_CONNECTION=192.168.1.37 33941 192.168.1.33 22
USER=francesco
_=/usr/bin/env
francesco@tya64:~$
I don't see the intel compiler variables set in there, nor an
LD_LIBRARY_PATH indicating where the intel libraries are located. See
my text from the last mail:
> I'm guessing that you're not sourcing the intel .sh files for
> non-interactive logins. You'll need to check your shell startup
files and
> ensure that those sourcing lines are executed when you login to
remote nodes
> non-interactively. E.g.:
>
> thisnode$ ssh othernode env | sort
>
> shows the relevant stuff in your environment on the other node.
Note that
> this is different than
>
> thisnode$ ssh othernode
> othernode$ env | sort
You might well have some logic in your .bashrc that quits before fully
executing when running non-interactive logins; hence, the ". /opt/
intel/fce/10.1.022/bin/ifortvars.sh" lines don't execute on the
192.168.1.33 machine when you run non-interactive jobs.
--
Jeff Squyres
Cisco Systems
