Yes, Dick has isolated the issue - novice users often believe Open MPI
(not their application) had a problem. Anything along the lines he suggests
can only help.
David
On 04/01/2010 01:12 AM, Richard Treumann wrote:
I do not know what the OpenMPI message looks like or why people want to
hide it. It should be phrased to avoid any implication of a problem with
OpenMPI itself.
How about something like this which:
"The application has called MPI_Abort. The application is terminated by
OpenMPI as the application demanded"
Dick Treumann - MPI Team
IBM Systems& Technology Group
Dept X2ZA / MS P963 -- 2455 South Road -- Poughkeepsie, NY 12601
Tele (845) 433-7846 Fax (845) 433-8363
From: "Jeff Squyres (jsquyres)"<jsquy...@cisco.com>
To:<david.single...@anu.edu.au>,<us...@open-mpi.org>
Date: 03/31/2010 06:43 AM
Subject: Re: [OMPI users] Hide Abort output
Sent by: users-boun...@open-mpi.org
At present there is no such feature, but it should not be hard to add.
Can you guys be a little more specific about exactly what you are seeing
and exactly what you want to see? (And what version you're working with -
I'll caveat my discussion that this may be a 1.5-and-forward thing)
-jms
Sent from my PDA. No type good.
----- Original Message -----
From: users-boun...@open-mpi.org<users-boun...@open-mpi.org>
To: Open MPI Users<us...@open-mpi.org>
Sent: Wed Mar 31 05:38:48 2010
Subject: Re: [OMPI users] Hide Abort output
I have to say this is a very common issue for our users. They repeatedly
report the long Open MPI MPI_Abort() message in help queries and fail to
look for the application error message about the root cause. A short
MPI_Abort() message that said "look elsewhere for the real error message"
would be useful.
Cheers,
David
On 03/31/2010 07:58 PM, Yves Caniou wrote:
Dear all,
I am using the MPI_Abort() command in a MPI program.
I would like to not see the note explaining that the command caused Open
MPI
to kill all the jobs and so on.
I thought that I could find a --mca parameter, but couldn't grep it. The
only
ones deal with the delay and printing more information (the stack).
Is there a mean to avoid the printing of the note (except the 2>/dev/null
tips)? Or to delay this printing?
Thank you.
.Yves.
