Ah - yet another set of options! :-)
Good suggestion, though...
On Apr 29, 2010, at 5:07 PM, Larry Baker wrote:
> Ralph,
>
> 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
Ralph,
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.
Larry Baker
US Geological Survey
650-329-5608
ba...@usgs.gov
On Apr 29, 2010, at 3:52
I ran into something this week that I think may require consideration by the
MPI Forum. Specifically, Rolf found a problem in their MTT runs where the tests
expect mpirun to return a non-zero exit status because one or more application
processes did so, even though all application procs terminat
Hi Ethan,
Bummer. What does the following command show?
sysctl -a | grep shm
Thanks!
--
Samuel K. Gutierrez
Los Alamos National Laboratory
On Apr 29, 2010, at 1:32 PM, Ethan Mallove wrote:
Hi Samuel,
I'm trying to run off your HG clone, but I'm seeing issues with
c_hello, e.g.,
$ mpirun
Can you pinpoint where you think the logic is incorrect? I can't easily see
where the parens are being added, and don't know anyone who checks/uses that
code path.
This hasn't been touched in a very long time, which makes me a tad cautious in
how this gets changed. Would need someone to either
Hi Samuel,
I'm trying to run off your HG clone, but I'm seeing issues with
c_hello, e.g.,
$ mpirun -mca mpi_common_sm sysv --mca btl self,sm,tcp --host
burl-ct-v440-2,burl-ct-v440-2 -np 2 ./c_hello
--
A system call fai
Cisco gives thumbs up on testing results. Ship it.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
Hi,
We had some trouble with a user using /bin/sh together with
openmpi/1.4.1 (Centos 5 on amd64 processors, intel compiler 11.1)
When spawning MPI processes on a different machine it gave errors such as
/bin/sh: -c: line 0: syntax error near unexpected token `('
/bin/sh: -c: line 0: `/usr/bin/e
On 29/4/2010 1:04 μμ, Jeff Squyres wrote:
On Apr 28, 2010, at 11:34 AM, Ioannis E. Venetis wrote:
1) We need to have support for both, a native and also a
cross-compilation environment.
a) The native environment is a non-mainstream 64-bit processor
(specially designed for the system where
On Apr 28, 2010, at 11:34 AM, Ioannis E. Venetis wrote:
> 1) We need to have support for both, a native and also a
> cross-compilation environment.
>a) The native environment is a non-mainstream 64-bit processor
> (specially designed for the system where it is being used). The OS
> environment
Hello Ralf,
Thank you for answering.
On 29/4/2010 9:02 πμ, Ralf Wildenhues wrote:
Hello Ioannis,
* Ioannis E. Venetis wrote on Wed, Apr 28, 2010 at 05:34:47PM CEST:
b) The cross-compilation environment should be run on a Linux x86_64
system. The cross-compiler, libraries, etc are already w
Hello Ioannis,
* Ioannis E. Venetis wrote on Wed, Apr 28, 2010 at 05:34:47PM CEST:
> b) The cross-compilation environment should be run on a Linux x86_64
> system. The cross-compiler, libraries, etc are already working, which
> means that only OpenMPI needs to be ported right now. We use this
>
12 matches
Mail list logo
