I¹m afraid that would be a rather significant job as it plays a rather
significant role in the ssh startup procedure. We have plans to revamp that
portion of the code, but without someone who knows exactly what is going on
and where, you are more likely to break it than revise it.
If you can live
Is there a place where I can hack the openmpi code to force it to keep
the ssh sessions open without the -d option? I looked through some of
the code, including orterun.c and a few other places, but don't have
the familiarity with the code to find the place.
Thanks!
Dave
Galen Shipman
Success! The -n option on ssh did the trick. Now, the question is is
there a way of leaving the ssh sessions open without doing the
debugging? With the debugging part on, it prints out lots of stuff that
I don't want to have to see every time I run my code. I know, I'm just
being picky.
Tha
-d leaves the ssh session open
Try using:
mpirun -d -host boxtop2 -mca pls_rsh_agent "ssh -X -n" xterm -e cat
Note the "ssh -X -n", this will tell ssh not to open stdin..
You should then be able to type characters in the resulting xterm and
have them echo'd back correctly.
- Galen
On Dec
On Fri, Dec 01, 2006 at 11:51:24AM +0100, Peter Kjellstrom wrote:
> This might be a bit naive but, if you spawn two procs on a dual core dual
> socket system then the linux kernel should automagically schedule them this
> way.
No, we checked this for OpenMP and MPI, and in both cases wiring the
Hi,
In my program I am calling MPI_Barrier(MPI_COMM_WORLD), but it seems to
cause an error on one node. The node changes depending on how many
total nodes I have (it could be 4 or 2). I'm thinking it's MPI_Barrier
because I put print statements around it and that's where the program
terminate
Thanks for the suggestion, but it doesn't fix my problem. I did the
same thing you did and was able to get xterms open when using the -d
option. But when I run my code, the -d option seems to play havoc with
stdin. My code normally reads stdin from one processor and it
broadcasts it to the oth
I think this might be as simple as adding "-d" to the mpirun command
line
If I run:
mpirun -np 2 -d -mca pls_rsh_agent "ssh -X" xterm -e gdb ./mpi-ping
All is well, I get the xterm's up..
If I run:
mpirun -np 2 -mca pls_rsh_agent "ssh -X" xterm -e gdb ./mpi-ping
I get the foll
What the system is saying is that (a) you don't have transparent ssh
authority on one or more of your nodes, and/or (b) the system was unable to
locate the Open MPI code libraries on the remote node. For the first
problem, please see the FAQ at:
http://www.open-mpi.org/faq/?category=rsh#ssh-keys
I 've got the same problem as described in:
http://www.open-mpi.org/community/lists/users/2006/07/1537.php
From: Chengwen Chen (chenchengwen_at_[hidden])
List-Post: users@lists.open-mpi.org
Date: 2006-07-04 03:53:26
The problem seems to occur randomly! It occurs more often if I use a
larger num
On Fri, Dec 01, 2006 at 09:35:09AM -0500, Brock Palen wrote:
> On Dec 1, 2006, at 9:23 AM, Gleb Natapov wrote:
>
> > On Fri, Dec 01, 2006 at 04:14:31PM +0200, Gleb Natapov wrote:
> >> On Fri, Dec 01, 2006 at 11:51:24AM +0100, Peter Kjellstrom wrote:
> >>> On Saturday 25 November 2006 15:31, shap..
On Dec 1, 2006, at 9:23 AM, Gleb Natapov wrote:
On Fri, Dec 01, 2006 at 04:14:31PM +0200, Gleb Natapov wrote:
On Fri, Dec 01, 2006 at 11:51:24AM +0100, Peter Kjellstrom wrote:
On Saturday 25 November 2006 15:31, shap...@isp.nsc.ru wrote:
Hello,
i cant figure out, is there a way with open-mpi
On Fri, Dec 01, 2006 at 04:14:31PM +0200, Gleb Natapov wrote:
> On Fri, Dec 01, 2006 at 11:51:24AM +0100, Peter Kjellstrom wrote:
> > On Saturday 25 November 2006 15:31, shap...@isp.nsc.ru wrote:
> > > Hello,
> > > i cant figure out, is there a way with open-mpi to bind all
> > > threads on a given
On Fri, Dec 01, 2006 at 11:51:24AM +0100, Peter Kjellstrom wrote:
> On Saturday 25 November 2006 15:31, shap...@isp.nsc.ru wrote:
> > Hello,
> > i cant figure out, is there a way with open-mpi to bind all
> > threads on a given node to a specified subset of CPUs.
> > For example, on a multi-socket
On Saturday 25 November 2006 15:31, shap...@isp.nsc.ru wrote:
> Hello,
> i cant figure out, is there a way with open-mpi to bind all
> threads on a given node to a specified subset of CPUs.
> For example, on a multi-socket multi-core machine, i want to use
> only a single core on each CPU.
> Thank
15 matches
Mail list logo
