On 8 Dec 2011, at 22:13, Jeff Squyres wrote:
> 1.4.5rc1 is now posted in the usual place:
>
>http://www.open-mpi.org/software/ompi/v1.4/
>
> Gearing up for a pre-Christmas release -- please test! There have only been
> a few bug fixes since 1.4.4. See
> http://svn.open-mpi.org/svn/ompi/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/12/11 08:33, Ralph Castain wrote:
> That param was intended to catch user-level mistakes
> whereby the user specified a tmpdir location via the
> tmpdir_base MCA param that the system admin wanted to
> protect. It was not intended for someone to
Well, I actually have to eat my words here. This code is alive and well.
However, I don't think it does what you wanted or perhaps expected.
That param was intended to catch user-level mistakes whereby the user specified
a tmpdir location via the tmpdir_base MCA param that the system admin wante
This is amusing - reviewing the code quickly, it appears that the supporting
code for orte_no_session_dir was mistakenly removed at some point.
I'll restore that functionality. Thanks for pointing it out!
On Dec 12, 2011, at 11:10 PM, Christopher Samuel wrote:
> -BEGIN PGP SIGNED MESSAGE---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/12/11 12:59, Jeff Squyres wrote:
> Fair enough. We've definitely seen cases where the
> /tmp filesystem *did* matter, so perhaps it's a kernel
> version issue, or a phase of the moon issue, or...
Well it's more where $TMPDIR points to, not rel
On Dec 13, 2011, at 5:56 PM, Christopher Samuel wrote:
>> Did David's suggestion help?
>
> It did, thanks - though I take David's point that there doesn't seem to
> be any measurable difference between using local storage (or even tmpfs)
> and Lustre for this so it seems like a warning that shoul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/12/11 07:44, David Singleton wrote:
> This is why I was hoping sites could be given the opportunity to control
> that warning message.
Just to confirm that I see negligible difference between Panasas, local
SATA drives and /dev/shm memory backe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/12/11 07:44, David Singleton wrote:
> Hi Chris,
Hello David!
> Try setting OMPI_MCA_orte_tmpdir_base.
That works, thanks!
> Going back to a related earlier OMPI users thread ("How to set up
> state-less node /tmp for OpenMPI usage"), here ar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/12/11 09:21, Jeff Squyres wrote:
> On Dec 13, 2011, at 1:10 AM, Christopher Samuel wrote:
>
> > I think you want s/settings/setting/ there.
>
> Fixed! Thanks.
Not a problem.
> > Also I can not seem to make it accept the orte_no_session_dir
>
On Dec 13, 2011, at 1:10 AM, Christopher Samuel wrote:
> It now complains that $TMPDIR points to our Panasas filesystem,
> and there's a minor typo in its message, saying:
>
> # Note, too, that system administrators can set a list of filesystems
> # where Open MPI is disallowed from creating tem
Hi Chris,
Try setting OMPI_MCA_orte_tmpdir_base.
Going back to a related earlier OMPI users thread ("How to set up state-less node /tmp for OpenMPI usage"), here are sm pingpong latencies (using 1.4.3) for
session dirs on Lustre, an SSD and tmpfs:
[dbs900@v1490 ~/MPI]$ export OMPI_MCA_orte_t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/12/11 09:13, Jeff Squyres wrote:
> Gearing up for a pre-Christmas release -- please test!
Had a quick test here (we're still on 1.4.2 as our default).
It now complains that $TMPDIR points to our Panasas filesystem,
and there's a minor typo in
12 matches
Mail list logo
