Thanks Jon.
I fear this falls into the "won't fix until I have some spare time" category -
probably won't get to it myself until Aug/Sept due to priorities.
In the interim, perhaps someone who has more priority in this area will step in
to fix it.
On Apr 30, 2010, at 3:15 PM, Jonathan Vincent
Hi,
The code path is used when the user has /bin/sh as their login shell.
There seemed to be seperate code paths depending on the login shell. I
guess it is not suprising noone has looked at this part for a long
time, /bin/sh is not a popular choice :D. It *should* be easily
reproduceable if you m
Guess this has been too upsetting a question - I'll work off-list with the
other developers to determine an appropriate OMPI behavior.
On Apr 30, 2010, at 9:28 AM, N.M. Maclaren wrote:
> On Apr 30 2010, Ralph Castain wrote:
>> On Apr 30, 2010, at 6:15 AM, Jeff Squyres wrote:
>>
MPI quite r
On Thu, Apr/29/2010 02:52:24PM, Samuel K. Gutierrez wrote:
> Hi Ethan,
>
> Bummer. What does the following command show?
>
> sysctl -a | grep shm
In this case, I think the Solaris equivalent to sysctl is prctl, e.g.,
$ prctl -i project group.staff
project: 10: group.staff
NAMEPRIV
On Apr 30 2010, Ralph Castain wrote:
On Apr 30, 2010, at 6:15 AM, Jeff Squyres wrote:
MPI quite rightly does not specify this, because the matter is very
system- dependent, and it is not possible to return the exit code (or
display it) in all environments. Sorry, but that is reality.
Correct
On Apr 30, 2010, at 6:15 AM, Jeff Squyres wrote:
> On Apr 30, 2010, at 5:59 AM, N.M. Maclaren wrote:
>
>> MPI quite rightly does not specify this, because the matter is very system-
>> dependent, and it is not possible to return the exit code (or display it)
>> in all environments. Sorry, but t
I just wanted to followup of this thread. I filed a ticket with all of
these issues since many of them are potential bugs that should be
fixed for v1.5 (and v1.4 if possible). The link to the ticket is below
if you wanted to follow the progress:
https://svn.open-mpi.org/trac/ompi/ticket/23
On Fri, 23 Apr 2010 at 11:29:53, George Bosilca wrote:
If you use any kind of high performance network that require memory
registration for communications, then this high cost for the
MPI_Alloc_mem will be hidden by the communications. However, the
MPI_Alloc_mem function seems horribly complic
On Fri, 23 Apr 2010 at 11:29:53, George Bosilca wrote:
If you use any kind of high performance network that require memory
registration for communications, then this high cost for the
MPI_Alloc_mem will be hidden by the communications. However, the
MPI_Alloc_mem function seems horribly complic
On Apr 30 2010, Jeff Squyres wrote:
The last paragraph of the specification of MPI_Finalize makes it clear
that it is the USER'S responsibility to return an exit code to the system
for process 0, and that what happens for other ones is undefined. Or
fairly clear - it could be stated in so many
On Apr 30, 2010, at 5:59 AM, N.M. Maclaren wrote:
> MPI quite rightly does not specify this, because the matter is very system-
> dependent, and it is not possible to return the exit code (or display it)
> in all environments. Sorry, but that is reality.
Correct -- MPI intentionally does not say
On Apr 30 2010, Larry Baker wrote:
I don't know if there is any standard ordering of non-zero exit status
codes. If so, another option would be to return the the largest
(smallest) value, when that is the most serious exit status.
There isn't, and some systems have used exit codes in othe
12 matches
Mail list logo
