This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
On 31/08/2007, Gleb Natapov <glebn_at_[hidden]> wrote:
> On Fri, Aug 31, 2007 at 08:04:00AM +0100, Simon Hammond wrote:
> > On 31/08/2007, Lev Givon <lev_at_[hidden]> wrote:
> > > Received from George Bosilca on Thu, Aug 30, 2007 at 07:42:52PM EDT:
> > > > I have a patch for this, but I never felt a real need for it, so I
> > > > never push it in the trunk. I'm not completely convinced that we need
> > > > it, except in some really strange situations (read grid). Why do you
> > > > need a port range ? For avoiding firewalls ?
> > We are planning on using OpenMPI as the basis for running MPI jobs
> > across a series of workstations overnight. The workstations are locked
> > down so that only a small number of ports are available for use. If we
> > try to use anything else its disaster.
> > Unfortunately this is really an organizational policy above anything
> > else and its very difficult to get it to change.
> As workaround you can write application that will bind to all ports that
> are not allowed to be used by MPI before running MPI job.
Sounds very drastic, thanks for the advice. I'll give it a go. Do you
think it might be easy to add this to the source code at sometime
Thanks for your advice guys,
University of Warwick
> users mailing list