On Apr 14, 2016, at 12:27 PM, Tom Rosmond wrote:
>
> Gilles,
>
> Yes, that solved the problem. Thanks for the help. I assume this fix will
> be in the next official release, i.e. 1.10.3?
Yup!
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/we
Gilles,
Yes, that solved the problem. Thanks for the help. I assume this fix
will be in the next official release, i.e. 1.10.3?
Tom Rosmond
On 04/13/2016 05:07 PM, Gilles Gouaillardet wrote:
Tom,
i was able to reproduce the issue with an older v1.10 version, but not
with current v1.10
Tom,
i was able to reproduce the issue with an older v1.10 version, but not
with current v1.10 from git.
could you please give a try to 1.10.3rc1 available at
https://www.open-mpi.org/software/ompi/v1.10/downloads/openmpi-1.10.3rc1.tar.bz2
?
Cheers,
Gilles
On 4/14/2016 4:05 AM, Tom Rosmo
Hello,
In this thread from the Open-MPI archives:
https://www.open-mpi.org/community/lists/devel/2014/03/14416.php
a strange problem with a system call is discussed, and claimed to be
solved. However, in running a simple test program with some new MPI-3
functions, the problem seems to be bac
Dear Users,
I have two separate program say PROG1 and PROG2 .Both programs run
parallel independently. But I have made following modifications.
PROG1 run first doing its own job and then preparing a input file for
PROG2, and then to run PROG2 call system is used.
The result of PROG2 is used in PRO
both versions so you
> would think both would fail if where an issue.
> Is there any way of reserving ports for non MPI use?
>
> From: Ralph Castain
> To: Open MPI Users
> Sent: Friday, 20 January 2012 10:30 AM
> Subject: Re: [OMPI users] system() call corrupts MPI process
AM
Subject: Re: [OMPI users] system() call corrupts MPI processes
Hi Randolph!
Sorry for delay - was on the road. This isn't an issue of corruption. What ORTE
is complaining about is that your perl script wound up connecting to the same
port that your process is listening on via ORTE. OR
I assume that the SIGCHLD was released after starting the daemon ie on return
of the system() call
From: Durga Choudhury
To: Open MPI Users
Sent: Friday, 20 January 2012 2:22 AM
Subject: Re: [OMPI users] system() call corrupts MPI processes
This is just a
Hi Randolph!
Sorry for delay - was on the road. This isn't an issue of corruption. What ORTE
is complaining about is that your perl script wound up connecting to the same
port that your process is listening on via ORTE. ORTE is rather particular
about the message format - specifically, it requi
This is just a thought:
according to the system() man page, 'SIGCHLD' is blocked during the
execution of the program. Since you are executing your command as a
daemon in the background, it will be permanently blocked.
Does OpenMPI daemon depend on SIGCHLD in any way? That is about the
only differ
Which network transport are you using, and what version of Open MPI are you
using? Do you have OpenFabrics support compiled into your Open MPI
installation?
If you're just using TCP and/or shared memory, I can't think of a reason
immediately as to why this wouldn't work, but there may be a sub
I have a section in my code running in rank 0 that must start a perl program
that it then connects to via a tcp socket.
The initialisation section is shown here:
sprintf(buf, "%s/session_server.pl -p %d &", PATH,port);
int i = system(buf);
printf("system returned %d\n", i);
Some ti
12 matches
Mail list logo
