Hi Ralph,
I have confirmed that openmpi-1.4a1r22335 works with my master, slave
example. The temporary directories are cleaned up properly.
Thanks for the help!
nick
On Thu, Dec 17, 2009 at 13:38, Nicolas Bock wrote:
> Ok, I'll give it a try.
>
> Thanks, nick
>
>
>
> On Thu, Dec 17, 2009 at
Ok, I'll give it a try.
Thanks, nick
On Thu, Dec 17, 2009 at 12:44, Ralph Castain wrote:
> In case you missed it, this patch should be in the 1.4 nightly tarballs -
> feel free to test and let me know what you find.
>
> Thanks
> Ralph
>
> On Dec 2, 2009, at 10:06 PM, Nicolas Bock wrote:
>
> Th
In case you missed it, this patch should be in the 1.4 nightly tarballs - feel
free to test and let me know what you find.
Thanks
Ralph
On Dec 2, 2009, at 10:06 PM, Nicolas Bock wrote:
> That was quick. I will try the patch as soon as you release it.
>
> nick
>
>
> On Wed, Dec 2, 2009 at 21:
That was quick. I will try the patch as soon as you release it.
nick
On Wed, Dec 2, 2009 at 21:06, Ralph Castain wrote:
> Patch is built and under review...
>
> Thanks again
> Ralph
>
> On Dec 2, 2009, at 5:37 PM, Nicolas Bock wrote:
>
> Thanks
>
> On Wed, Dec 2, 2009 at 17:04, Ralph Castain
Patch is built and under review...
Thanks again
Ralph
On Dec 2, 2009, at 5:37 PM, Nicolas Bock wrote:
> Thanks
>
> On Wed, Dec 2, 2009 at 17:04, Ralph Castain wrote:
> Yeah, that's the one all right! Definitely missing from 1.3.x.
>
> Thanks - I'll build a patch for the next bug-fix release
>
Thanks
On Wed, Dec 2, 2009 at 17:04, Ralph Castain wrote:
> Yeah, that's the one all right! Definitely missing from 1.3.x.
>
> Thanks - I'll build a patch for the next bug-fix release
>
>
> On Dec 2, 2009, at 4:37 PM, Abhishek Kulkarni wrote:
>
> > On Wed, Dec 2, 2009 at 5:00 PM, Ralph Castain
Yeah, that's the one all right! Definitely missing from 1.3.x.
Thanks - I'll build a patch for the next bug-fix release
On Dec 2, 2009, at 4:37 PM, Abhishek Kulkarni wrote:
> On Wed, Dec 2, 2009 at 5:00 PM, Ralph Castain wrote:
>> Indeed - that is very helpful! Thanks!
>> Looks like we aren't
On Wed, Dec 2, 2009 at 5:00 PM, Ralph Castain wrote:
> Indeed - that is very helpful! Thanks!
> Looks like we aren't cleaning up high enough - missing the directory level.
> I seem to recall seeing that error go by and that someone fixed it on our
> devel trunk, so this is likely a repair that did
Indeed - that is very helpful! Thanks!
Looks like we aren't cleaning up high enough - missing the directory level. I
seem to recall seeing that error go by and that someone fixed it on our devel
trunk, so this is likely a repair that didn't get moved over to the release
branch as it should have
On Wed, Dec 2, 2009 at 14:23, Ralph Castain wrote:
> Hmmif you are willing to keep trying, could you perhaps let it run for
> a brief time, ctrl-z it, and then do an ls on a directory from a process
> that has already terminated? The pids will be in order, so just look for an
> early number (
Hmmif you are willing to keep trying, could you perhaps let it run for a
brief time, ctrl-z it, and then do an ls on a directory from a process that has
already terminated? The pids will be in order, so just look for an early number
(not mpirun or the parent, of course).
It would help if yo
On Wed, Dec 2, 2009 at 12:12, Ralph Castain wrote:
>
> On Dec 2, 2009, at 10:24 AM, Nicolas Bock wrote:
>
>
>
> On Tue, Dec 1, 2009 at 20:58, Nicolas Bock wrote:
>
>>
>>
>> On Tue, Dec 1, 2009 at 18:03, Ralph Castain wrote:
>>
>>> You may want to check your limits as defined by the shell/system
On Dec 2, 2009, at 10:24 AM, Nicolas Bock wrote:
>
>
> On Tue, Dec 1, 2009 at 20:58, Nicolas Bock wrote:
>
>
> On Tue, Dec 1, 2009 at 18:03, Ralph Castain wrote:
> You may want to check your limits as defined by the shell/system. I can also
> run this for as long as I'm willing to let it r
On Tue, Dec 1, 2009 at 20:58, Nicolas Bock wrote:
>
>
> On Tue, Dec 1, 2009 at 18:03, Ralph Castain wrote:
>
>> You may want to check your limits as defined by the shell/system. I can
>> also run this for as long as I'm willing to let it run, so something else
>> appears to be going on.
>>
>>
>>
On Tue, Dec 1, 2009 at 18:03, Ralph Castain wrote:
> You may want to check your limits as defined by the shell/system. I can
> also run this for as long as I'm willing to let it run, so something else
> appears to be going on.
>
>
>
Is that with 1.3.3? I found that with 1.3.4 I can run the exampl
You may want to check your limits as defined by the shell/system. I can also
run this for as long as I'm willing to let it run, so something else appears to
be going on.
On Dec 1, 2009, at 4:38 PM, Nicolas Bock wrote:
>
>
> On Tue, Dec 1, 2009 at 16:28, Abhishek Kulkarni wrote:
> On Tue, De
On Tue, Dec 1, 2009 at 16:28, Abhishek Kulkarni wrote:
> On Tue, Dec 1, 2009 at 6:15 PM, Nicolas Bock
> wrote:
> > After reading Anthony's question again, I am not sure now that we are
> having
> > the same problem, but we might. In any case, the attached example
> programs
> > trigger the issue
On Tue, Dec 1, 2009 at 6:15 PM, Nicolas Bock wrote:
> After reading Anthony's question again, I am not sure now that we are having
> the same problem, but we might. In any case, the attached example programs
> trigger the issue of running out of pipes. I don't see how orted could, even
> if it was
Linux mujo 2.6.30-gentoo-r5 #1 SMP PREEMPT Thu Sep 17 07:47:12 MDT 2009
x86_64 Intel(R) Core(TM)2 Quad CPU Q8200 @ 2.33GHz GenuineIntel GNU/Linux
On Tue, Dec 1, 2009 at 16:24, Ralph Castain wrote:
> It really does help if we have some idea what OMPI version you are talking
> about, and on what k
Sorry,
openmpi-1.3.3 compiled with gcc-4.4.2
nick
On Tue, Dec 1, 2009 at 16:24, Ralph Castain wrote:
> It really does help if we have some idea what OMPI version you are talking
> about, and on what kind of platform.
>
> This issue was fixed to the best of my knowledge (not all the pipes were
It really does help if we have some idea what OMPI version you are talking
about, and on what kind of platform.
This issue was fixed to the best of my knowledge (not all the pipes were
getting closed), but I would have to look and see what release might contain
the fix...would be nice to know w
After reading Anthony's question again, I am not sure now that we are having
the same problem, but we might. In any case, the attached example programs
trigger the issue of running out of pipes. I don't see how orted could, even
if it was reused. There is only a very limited number of processes run
Hello list,
a while back in January of this year, a user (Anthony Thevenin) had the
problem of running out of open pipes when he tried to use MPI_Comm_spawn a
few times. As I the thread his started in the mailing list archives and have
just joined the mailing list myself, I unfortunately can't rep
23 matches
Mail list logo
