Hello @ all,
Short question: How to select what is the behavior of --output-filename?
Long question:
I am used to that the option --output-filename file.out will generate the files
file.out.0 file.out.1 etc.
The default logic switched to file.out/1/rank.*/stdout
man mpirun gives me:
-output-filename, --output-filename <filename>
Redirect the stdout, stderr, and stddiag of all processes to a
process-unique version of the specified filename. ...
mpirun --help output gives me:
-output-filename|--output-filename <arg0>
Redirect output from application processes into
filename/job/rank/std[out,err,diag]. A relative
path value will be converted to an absolute path
So man is reporting a wrong logic, help provides the correct answer for the
logic. A lock in the code yields that the output from man comes from
./orte/orted/orted_main.c:
{ "orte_output_filename", '\0', "output-filename", "output-filename", 1,
NULL, OPAL_CMD_LINE_TYPE_STRING,
"Redirect output from application processes into filename.rank" },
The mpirun output comes from
./orte/mca/schizo/ompi/schizo_ompi.c
{ "orte_output_filename", '\0', "output-filename", "output-filename", 1,
&orte_cmd_options.output_filename, OPAL_CMD_LINE_TYPE_STRING,
"Redirect output from application processes into
filename/job/rank/std[out,err,diag]. A relative path value will be converted to
an absolute path",
OPAL_CMD_LINE_OTYPE_OUTPUT },
These two behaviors can probably be selected with some mca parameters, but I
could not figure out which one.
So the final question: How can I configure which default backend is used for
the command line parameter --output-filename?
Best regards
Max Sagebaum
uname -a: 5.3.8-200.fc30.x86_6
ompi_info:
Package: Open MPI
mockbu...@buildvm-08.phx2.fedoraproject.org<mailto:mockbu...@buildvm-08.phx2.fedoraproject.org>
Distribution
Open MPI: 3.1.4
Open MPI repo revision: v3.1.4
Open MPI release date: Apr 15, 2019
Open RTE: 3.1.4
Open RTE repo revision: v3.1.4
Open RTE release date: Apr 15, 2019
OPAL: 3.1.4
OPAL repo revision: v3.1.4
OPAL release date: Apr 15, 2019
MPI API: 3.1.0
Ident string: 3.1.4
Prefix: /usr/lib64/openmpi
Configured architecture: x86_64-unknown-linux-gnu
Configure host: buildvm-08.phx2.fedoraproject.org
Configured by: mockbuild
Configured on: Thu Oct 17 03:20:12 UTC 2019
Configure host: buildvm-08.phx2.fedoraproject.org
Configure command line: '--prefix=/usr/lib64/openmpi'
'--mandir=/usr/share/man/openmpi-x86_64'
'--includedir=/usr/include/openmpi-x86_64' '--sysconfdir=/etc/openmpi-x86_64'
'--disable-silent-rules' '--enable-builtin-atomics'
'--enable-mpi-thread-multiple' '--enable-mpi-cxx' '--enable-mpi-java'
'--with-sge' '--with-
valgrind' '--enable-memchecker' '--with-hwloc=/usr' '--with-libevent=external'
'--with-pmix=external' 'CC=gcc' 'CXX=g++' 'LDFLAGS=-Wl,-z,relro -Wl,--as-needed
-Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld' 'CFLAGS= -O2 -g
-pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2
-Wp,-D_GLIBCXX_ASSERTION
S -fexceptions -fstack-protector-strong -grecord-gcc-switches
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic
-fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection'
'CXXFLAGS= -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOU
RCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong
-grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic
-fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection'
'FC=gfortran' 'FCFLAGS= -O2 -g -pipe -Wall
-Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS
-fexceptions -fstack-protector-strong -grecord-gcc-switches
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic
-fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection'
Built by: mockbuild
...
If required I can post the full output.
