If Dave says it's ok then it must be! :)
(Thanks for the explanation)
> On 11 Nov 2015, at 23:04 , Ralph Castain wrote:
>
> Every orted maintains knowledge of where every process in the DVM is located
> in case some local client needs information or to otherwise communicate
> out-of-band with
Every orted maintains knowledge of where every process in the DVM is located in
case some local client needs information or to otherwise communicate
out-of-band with some non-local peer. The RTE has no idea of the possible
communication pattern, so we err on the side of more info to avoid someti
> On 11 Nov 2015, at 22:43 , Ralph Castain wrote:
> You must have the “-d” option set on the orte-dvm cmd line?
Yes.
> You’ll get one of those from every daemon in the job each time you launch an
> app.
Ok, that explains the number better :)
Why is every orted aware of a job on another orted?
You must have the “-d” option set on the orte-dvm cmd line? You’ll get one of
those from every daemon in the job each time you launch an app.
> On Nov 11, 2015, at 1:03 PM, Mark Santcroos
> wrote:
>
> Hi,
>
> I'm seeing this message an awful amount of times. (I.e. orders of magnitude
> more
Hi,
I'm seeing this message an awful amount of times. (I.e. orders of magnitude
more than I launch processes)
[nid15897:18424] [[2305,0],103] orted:comm:process_commands() Processing
Command: ORTE_DAEMON_ADD_LOCAL_PROCS
How should I interpret that?
Thanks
Mark
