On Oct 13, 2008, at 11:59 PM, Ralf Wildenhues wrote:
>> In general, LAM/MPI and Open MPI both require the ability of open
>> random
>> TCP ports between the hosts that you'll be using. So you should
>> either
>> disable the firewall, or add exceptions to allow any TCP connections
>> between the hosts that you'll be using.
>
> Do they require open random ports *at configure time*, on the system
> where configure is run?
It's been a looooong time since I've looked at LAM's configure code,
so I don't know offhand. I'm quite sure that we don't open random
sockets between two different hosts in configure (configure never gets
information about a 2nd host). If we open sockets, we only open them
in a single process.
FWIW: a quick grep through configure doesn't show any calls to bind(),
connect(), or accept(). So I don't know why Windows firewall is
complaining during running configure.
As I specified earlier, we have done little/no testing with Cygwin
(last Cygwin testing was several years ago -- possibly even in the
90's?). So we don't really know why these weird things are
happening. Given that all of our effort is on Open MPI these days, I
doubt whether any of the original LAM developers will be looking into
Cygwin issues.
--
Jeff Squyres
Cisco Systems
|
