emre brookes wrote:
George Reeke wrote:
On Tue, 2018-09-04 at 16:08 -0500, emre brookes wrote:
Is there some setting to turn off the extra messages generated by
openmpi ?
----------
which strangely goes to stdout and not stderr.
I would intuitively expect error or notice messages to go to stderr.
Is there a way to redirect these messages to stderr or some
specified file?
----------
I need to separate this from the collected stdout of the job processes
themselves.
Any suggestions as to a more elegant or standard way of dealing with
this?
TIA,
Emre.
I use an environment variable to name a path for my standard output.
My code, when it finds that variable, opens that file and writes
everything to it instead of stdout (I write from the Rank 0 node
only). Then openmpi (or slurm) can write to stdout all it wants.
George Reeke
Yes, that is another option, but is a bit difficult in my case,
as I have a framework for job submission and the job executable will come
from other developers and I don't want to put this restriction on them,
so I really need to capture the original standard out.
But perhaps I could write a wrapper to do this.
On further thought, this may be the way to go.
Yep, works great:
cap_stdout.sh:
---
#!/bin/bash
my_job > my_job.stdout
---
$ mpirun -np 2 cap_stdout.sh
(of course cap_stdout.sh can be fancied up with passing arguments for
executable, its params, stdout filename or other things)
Thanks again.
Emre
_______________________________________________
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users
