Gar - have to eat my words a bit. The jobid requested by orte-ps is just the
"local" jobid - i.e., it is expecting you to provide a number from 0-N, as I
described below (copied here):
> A jobid of 1 indicates the primary application, 2 and above would specify
> comm_spawned jobs.
Not providi
hello,
I'm trying to add a module into open-mpi MCA framework.
I hope the module could be conditionally compiled and linked.
It should be disabled by default and enabled by certain flags at configure
step.
When I make a dynamic module, everything is working fine.
The problem is that when I make a
Whenever I run valgrind on orterun (or any OMPI tool), I get the following
error msg:
--
A system call failed during shared memory initialization that should
not have. It is likely that your MPI job will now either abort or
Okay, you should have it in r24929. Use:
orte-ps --parseable
to get the new output.
On Jul 23, 2011, at 11:43 AM, Ralph Castain wrote:
> Gar - have to eat my words a bit. The jobid requested by orte-ps is just the
> "local" jobid - i.e., it is expecting you to provide a number from 0-N, as I
On 23 Jul 2011, at 03:55, Ralph Castain wrote:
>> c) A more easily parsable output format from ompi-ps. It doesn't need to be
>> a full blown XML format, just something like the following would suffice:
>>
>> jobid:719585280:state:Running:slots:1:num procs:4
>> process_name:./x:rank:0:pid:3082:n
On Jul 23, 2011, at 5:04 PM, Ashley Pittman wrote:
>
> On 23 Jul 2011, at 03:55, Ralph Castain wrote:
>>> c) A more easily parsable output format from ompi-ps. It doesn't need to be
>>> a full blown XML format, just something like the following would suffice:
>>>
>>> jobid:719585280:state:Runn
Hi Ralph,
That's mine - I'll take a look.
Thanks,
Sam
> Whenever I run valgrind on orterun (or any OMPI tool), I get the following
> error msg:
>
> --
> A system call failed during shared memory initialization that should
>
