c OSX 10.4.4 (ie, define a range of ports,
TCP and/or UDP). Since this is clearly critical, I suspect that I
must have overlooked some information on the OpenMPI web-site - if
so, please direct me to it. If I haven't, it might be worth a word or
two in the F
s work one
time for each process - the second time MPI_Send is called by process
0, there is a hang.
I am using Mac OSX 10.4.4 and gcc 4.0.1 on both systems, with OpenMPI
1.0.1 installed (compiled from sources). The small tutoria
Jeff,
Thanks for your responses.
On Feb 12, 2006, at 5:23 PM, Jeff Squyres wrote:
On Feb 10, 2006, at 12:18 PM, James Conway wrote:
Open MPI uses random port numbers for all it's communication.
(etc)
Thanks for the explanation. I will live with the open Firewall, and
look at the ipfw
progressing to real
MPI software (which I have kindly been given).
Best regards,
James Conway
------
James Conway, PhD.,
Department of Structural Biology
University of Pittsburgh School of Medicine
Biomedical Science Tower 3, Room 204
The patch for limiting the port range used by OpenMPI sounds useful.
This *is* an issue with firewalls. For a dedicated cluster behind a
firewall that's ok, but for harnessing available hardware (eg, Mac
OSX systems) in the wee hours its not. Gets my vote!
James Conway
On Aug 31, 200
t is intended or not.
This particular error can be avoided by excluding xgrid:
./configure CC=icc CXX=icpc F77=ifort F90=ifort --without-xgrid
James Conway
PS. Please note that the instructions for collecting install and make
information are not quite right, maybe out-of-date. On this page
