Greetings,
I have been pounding my head trying to get a large Fortran/MPI
package to work on MacOSX with ifort and openmpi. This is a MacBook
Pro with core duo. I do NOT believe the fault lies with openmpi;
however, after searching the archives, I will ask the list for
assistance.
1) I
On 3/12/07 2:18 PM, "Reuti" wrote:
> Am 12.03.2007 um 20:36 schrieb Ralph Castain:
>
>> ORTE propagates the signal to the application processes, but the ORTE
>> daemons never actually look at the signal themselves (looks just
>> like a
>> message to them). So I'm a little puzzled by that erro
Am 12.03.2007 um 20:36 schrieb Ralph Castain:
ORTE propagates the signal to the application processes, but the ORTE
daemons never actually look at the signal themselves (looks just
like a
message to them). So I'm a little puzzled by that error message
about the
"daemon received signal 12" -
It's supposed to be...but several of us have found it "blocking" somewhere
in the OPAL subdirectory tree.
On 3/12/07 2:06 PM, "Ben Allan" wrote:
> A build-related questions about 1.1.4
> Is parallel make usage (make -j 8) supported (at least if make is gnu?).
>
> thanks,
> Ben
>
> ___
A build-related questions about 1.1.4
Is parallel make usage (make -j 8) supported (at least if make is gnu?).
thanks,
Ben
Hmmmwell, the fact is that OpenMPI may not support LSF in the sense you
may be asking. As you have noticed, we don't actually read LSF enviro
variables to get the allocated node info nor interface to LSF for launch.
Obviously, as you have done, there are ways to work around that limitation.
We
What is the status of LSF and OpenMPI?
I'm running on a major HPC system using GM & LSF and we have to use a
number of workarounds so that we can use OpenMPI. Specifically,
using the scripts on this system we have to have our csh file source
a file to set up the environment on the nodes.
Am 12.03.2007 um 20:22 schrieb Pak Lui:
Hi Mark,
Olesen, Mark wrote:
I'm testing openmpi 1.2rc1 with GridEngine 6.0u9 and ran into
interesting
behaviour when using the qsub -notify option.
With -notify, USR1 and USR2 are sent X seconds before sending STOP
and KILL
signals, respectively.
ORTE propagates the signal to the application processes, but the ORTE
daemons never actually look at the signal themselves (looks just like a
message to them). So I'm a little puzzled by that error message about the
"daemon received signal 12" - I suspect that's just a misleading message
that was s
Am 12.03.2007 um 19:55 schrieb Ralph Castain:
I'll have to look into it - I suspect this is simply an erroneous
message
and that no daemon is actually being started.
I'm not entirely sure I understand what's happening, though, in
your code.
Are you saying that mpirun starts some number of a
Hi Mark,
Olesen, Mark wrote:
I'm testing openmpi 1.2rc1 with GridEngine 6.0u9 and ran into interesting
behaviour when using the qsub -notify option.
With -notify, USR1 and USR2 are sent X seconds before sending STOP and KILL
signals, respectively.
When the USR2 signal is sent to the process gro
I'll have to look into it - I suspect this is simply an erroneous message
and that no daemon is actually being started.
I'm not entirely sure I understand what's happening, though, in your code.
Are you saying that mpirun starts some number of application processes which
run merrily along, and the
Dear ompi users,
I am using OpenMPI in order to parallelize an evolutionary algorithm.
During the execution of the algorithm I have to send many same messages to
some nodes. So, in order to generate and use these messages i use MPI_Pack
and MPI_Unpack Each message has the following structure:
I'm testing openmpi 1.2rc1 with GridEngine 6.0u9 and ran into interesting
behaviour when using the qsub -notify option.
With -notify, USR1 and USR2 are sent X seconds before sending STOP and KILL
signals, respectively.
When the USR2 signal is sent to the process group with the mpirun process, I
re
14 matches
Mail list logo
