Ralph, thanks very much for your continued support:
Ralph Castain wrote:
I'd say that this behavior of mpirun under Torque TM should be considered as
a bug. Ideally, users should not have to design their scripts differently
according to whether the sysadmin decided to configure in TM or not.
Als
Ralph Castain wrote:
We would consider it a "feature" that OpenMPI is integrated with Torque. We
actually read the PBS_NODEFILE internally ourselves. I believe the problem
here is that specifying the "machinefile" prevents us from using that
Torque-integrated code and forces us down a different c
Bas hit the nail on the head: When using OpenMPI's mpirun under
Torque TM one apparently *must* omit the "-machinefile $PBS_NODEFILE"
flags and only specify "-np 2", presumably because TM knows all
about the machines under its control.
This behavior is new to me: Is this a feature or a bug in O
Thanks for the suggestion. I inserted a printenv command and the path and
library variables seem to be correct for our OpenMPI installation:
LD_LIBRARY_PATH=/usr/local/openmpi-1.2.1-pgi/lib:/opt/intel/compiler90/lib
MPIHOME=/usr/local/openmpi-1.2.1-pgi
PATH=/usr/local/openmpi-1.2.1-pgi/bin:/usr/
ot;
rpmbuild_options=${rpmbuild_options}" --define 'install_in_opt 0' --define
'install_shell_scripts 1' --define 'install_modulefile 0'"
rpmbuild_options=${rpmbuild_options}" --define '_prefix ${prefix}'"
build_single=yes
--
Ole Holm Nielsen
Department of Physics, Technical University of Denmark
