On 5 August 2008 at 17:43, Alexander Achenbach wrote: | Package: openmpi-bin | Version: 1.2.7~rc2-1 | Tags: lenny | | The openmpi-bin package adds an alternative 'mpiexec' that controls | /usr/bin/mpiexec and its manpage. | | However, another MPI implementation (lam-runtime) adds a single | alternative class 'mpirun' that includes the 'mpiexec' command and | its manpage as a slave. | | This causes alternatives resolution to be order dependent: Even | though lam-runtime adds the slave 'mpiexec' along with 'mpirun' | at priority 30, 'mpiexec' may get overridden if openmpi-bin gets | installed (or configured) after it. | | (On etch, a similar problem exists, except that 'mpiexec' also | includes the 'mpirun' command, extending the problem to its scope.) | | What about merging openmpi-bin's 'mpiexec' alternative as a slave | into 'mpirun'?
Manuel brought up the possible issue with symmetry, or lack thereof, regarding MPICH. I personally switched to using orterun as the frontend, or even slurm's tools, so I can't really comment. Further, lam is not all that actively managed inside Debian and upstream, so I would simply suggest to make the problem go away ... by purging lam. Is that an option for you? Dirk -- Three out of two people have difficulties with fractions. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
