We configure Torque on our cluster to set TMPDIR so that it points into a local file system on each node. A number of applications running on the cluster take advantage of TMPDIR. However, because the path is very long, TMPDIR causes mpd to fail. To avoid this problem, we set I_MPI_MPD_TMPDIR to /tmp. This works without a problem for Intel MPI 3.2.2, but with 4.0.0, a spurious error message appears on standard out stating that "Can't open file /tmp/mpd2.logfile...". For example, launching the test.c sample program with the mpirun command in a Torque script we get the following.
Hello world: rank 0 of 5 running on compute-1-18.local
Hello world: rank 1 of 5 running on compute-1-18.local
Hello world: rank 2 of 5 running on compute-1-18.local
Hello world: rank 3 of 5 running on compute-1-18.local
Hello world: rank 4 of 5 running on compute-1-16.local
Can't open file /tmp/mpd2.logfile_xxxxxxxx_490898.xxxxxx.xx_22680: [Errno 2] No such file or directory: '/tmp/mpd2.logfile_xxxxxxxx_490898.xxxxxx.xx_22680'
Unsetting TMPDIR and I_MPI_MPD_TMPDIR avoids the problem, but this is impratical as serveral apps depend on TMPDIR.
How can we prevent this error message from appearing?
