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.
I don't know if there is a way to do it in configure, but after installing you
can go into the $prefix/lib/openmpi directory and delete mca_btl_tcp.*
This will remove the tcp component and thus users will not be able to use it.
Note that you must NOT delete the mca_oob_tcp.* files, as these are used for
our internal administrative messaging and we currently require it to be
On Tuesday 21 November 2006 07:49 pm, Adam Moody wrote:
> We have some clusters which consist of a large pool of 8-way nodes
> connected via ethernet. On these particular machines, we'd like our
> users to be able to run 8-way MPI jobs on node, but we *don't* want them
> to run MPI jobs across nodes via the ethernet. Thus, I'd like to
> configure and build OpenMPI to provide shared memory support (or TCP
> loopback) but disable general TCP support.
> I realize that you can run without tcp via something like "mpirun --mca
> btl ^tcp", but this is up to the user's discretion. I need a way to
> disable it systematically. Is there a way to configure it out at build
> time or is there some runtime configuration file I can modify to turn it
> off? Also, when we configure "--without-tcp", the configure script
> doesn't complain, but TCP support is added anyway.
> -Adam Moody
> MPI Support @ LLNL
> users mailing list