Hello,
> Is the path correct for the new location?
yes, the $PATH points to the location of the sole static "mpirun" and of the
share/openmpi/*.txt directory.
Why is mpirun constructing $/etc/openmpi-default-hostfile as I
see in the error message below ?
(
/home/ilias/work/dirac/build_Intel
Hi,
yesterday I installed openmpi-1.6.2rc5r27346 and it seems to work.
Unfortunately I get a misleading error message when I call "mpiexec"
with an unknown option.
tyr fd1026 112 mpiexec -np 2 -host sunpc0 -report-bindings -bycore \
-bind-to-core date
Sun Sep 23 11:28:45 CEST 2012
[sunpc0:12881
Hi,
yesterday I installed openmpi-1.7a1r27358 and it has an improved
error message compared to openmpi-1.6.2, but doesn't show process bindings
and has some other problems as well.
"sunpc0" and "linpc0" are equipped with two dual-core processors running
Solaris 10 x86_64 and Linux x86_64 resp. "
Hi,
yesterday I installed openmpi-1.9a1r27359 and it doesn't report process
bindings on Solaris 10 x86_64 and Linux x86_64. As I showed in my previous
email for openmpi-1.7, it worked for openmpi-1.6.2.
tyr fd1026 114 mpiexec -np 2 -host sunpc0 -report-bindings \
-map-by core -bind-to core date
On Sep 22, 2012, at 11:11 PM, Ilias Miroslav wrote:
> Hello,
>
>> Is the path correct for the new location?
>
> yes, the $PATH points to the location of the sole static "mpirun" and of the
> share/openmpi/*.txt directory.
>
> Why is mpirun constructing $/etc/openmpi-default-hostfile as
> I
We chose not to backport the "unknown option" code as it proved too big a
change for a stable release series.
On Sep 23, 2012, at 2:37 AM, Siegmar Gross
wrote:
> Hi,
>
> yesterday I installed openmpi-1.6.2rc5r27346 and it seems to work.
> Unfortunately I get a misleading error message when I
Hmmm...works fine for me on Linux x86_64
[rhc@bend001 svn-trunk]$ mpirun -n 4 -host bend002 -report-bindings -map-by
core -bind-to core date
[bend002:04730] MCW rank 3 bound to socket 1[core 2[hwt
0-1]]:[../../../BB/../..]
[bend002:04730] MCW rank 0 bound to socket 0[core 0[hwt
0-1]]:[BB/../../
The 1.7 series has a completely different way of handling node topology than
was used in the 1.6 series. It provides some enhanced features, but it does
have some drawbacks in the case where the topology info isn't correct. I fear
you are running into this problem (again).
All the commands you
