On Apr 1, 2008, at 2:12 PM, Ralph H Castain wrote:
Sure - I'll rename it "orte_tmpdir_base" so it shows up.
Perfect, do we also need to carry on support for "OMPI_MCA_tmdir_base"?
- Galen
On 4/1/08 12:05 PM, "Shipman, Galen M." <gship...@ornl.gov> wrote:
On Apr 1, 2008, at 1:47 PM, Ralph H Castain wrote:
Ummm...actually, there already is an MCA param that does precisely
that:
OMPI_MCA_tmpdir_base
Perhaps we can modify this so that it reports in ompi_info?
- galen
Been there for years...sets the tmpdir for both orteds and procs.
The tmpdir argument for mpirun is there if you want to ONLY set the
tmpdir
base for mpirun. It provides a protective mechanism for cases where
the head
node is configured differently than the compute nodes.
Ralph
On 3/31/08 2:10 PM, "Aurélien Bouteiller" <boute...@eecs.utk.edu>
wrote:
I more than agree with Galen.
Aurelien
Le 31 mars 08 à 16:00, Shipman, Galen M. a écrit :
Slightly OT but along the same lines..
We currently have an argument to mpirun to set the HNP tmpdir (--
tmpdir).
Why don't we have an mca param to set the tmpdir for all the
orted's
and such?
- Galen
On Mar 31, 2008, at 3:51 PM, George Bosilca wrote:
I looked over the code and I don't see any problems with the
changes. The only think I did is replacing the getenv("HOME") by
opal_home_directory ...
Here is the logic for selecting the TMP directory:
if( NULL == (str = getenv("TMPDIR")) )
if( NULL == (str = getenv("TEMP")) )
if( NULL == (str = getenv("TMP")) )
if( NULL == (str = opal_home_directory()) )
str = ".";
Do you have any of those (TMPDIR, TEMP or TMP) in your
environment ?
george.
On Mar 31, 2008, at 3:13 PM, Josh Hursey wrote:
So does anyone know why the session directories are in $HOME
instead
of /tmp?
I'm using r18044 and every time I run the session directories
are
created in $HOME. George does this have anything to do with your
commits from earlier?
-- Josh
_______________________________________________
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel
_______________________________________________
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel
_______________________________________________
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel
_______________________________________________
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel
_______________________________________________
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel
_______________________________________________
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel
_______________________________________________
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel
