This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
On Apr 16, 2009, at 11:29 AM, Francesco Pietra wrote:
> francesco_at_tya64:~$ ssh 192.168.1.33 env | sort
> SSH_CLIENT=192.168.1.37 33941 22
> SSH_CONNECTION=192.168.1.37 33941 192.168.1.33 22
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.