Someone correctly pointed out the bug in my examples. In the MPI_Put I
pass a 0 as the displacement, however, the argument must be of type
integer (kind=MPI_ADDRESS_KIND), which is NOT the default integer type.
Replacing the 0 with the correct integer type fixes both examples. Now
to see if it fi
Both look perfectly right to me. The difference is only because your "success"
one still has the ssh session active.
It looks to me like something is preventing communication when the ssh session
is terminated, but I have no clue why.
Given the small cluster size, I would just add this to your
On Wed, Dec 29, 2010 at 10:10 AM, Advanced Computing Group University of
Padova wrote:
> Thank you Ralph,
> Your suspects seems to be quite interesting :)
> I try to run the same program from node 192.168.1/2.11 using also
> 192.168.2.12 "tracing" .12 activities.
> I attach the two files (_succ:
Thank you Ralph,
Your suspects seems to be quite interesting :)
I try to run the same program from node 192.168.1/2.11 using also
192.168.2.12 "tracing" .12 activities.
I attach the two files (_succ: using --debug-daemons , _fail:without
--debug-daemons)
I notice that orted daemon on the second nod
Jeff, Shiqing, anyone...
I notice there's no Fortan support in the Windows binary versions of
1.5.1 on the website. Is that a deliberate decision?
Damien
