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.
As a quick answer before I go to study yous and Douglas mail: the
desktop toward which I was sshing is a single processor 10-years old
desktop with nothing about intel or openmpi. It only has ssh software
to run amber procedures on remote machines. I can try your suggested
ssh toward a parallel computer, but, in any case, my running of
openmpi and Amber is normally on single-node uma-type computers.
Nothing outside them is involved in the parallel calculation. It is
the situation described by Douglas. The computation should work (and
it worked in the past) even if the computer is removed from the
On Thu, Apr 16, 2009 at 5:37 PM, Jeff Squyres <jsquyres_at_[hidden]> wrote:
> 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.
> Jeff Squyres
> Cisco Systems
> users mailing list