Re: [mpich2-core] mpd vs. mpd
In terms of documentation, one option is that we can de-emphasize the use of mpd.py(or mpd, pmpd, mpddaemon or mpdd) altogether, instead we recommend users to use "mpdboot -n 1" instead of "mpd.py &" to minimize the jolt to users. (Ralph, is "mpdboot -n 1" works as well as "mpd &" ?) Since the music player can be installed before or after mpich2, we are stuck to resolve the name conflict issue. A.Chan ----- "Rusty Lusk" <[email protected]> wrote:
Ralph and I think we are OK with mpd.py, but doesn't this invalidate
tons of documentation? Perhaps better would be "mpddaemon" or "mpdd",
to remain parallel to the other mpd-related executables like mpdcheck,
mpdtrace, etc. Even then, changing things would be quite a jolt for
users. Could there be an option to rename mpdd to mpd if you aren't
using the music player? Perhaps I don't completely understand the problem.
On Sunday,Mar 29, 2009, at 10:25 PM, Pavan Balaji wrote:
I'm actually waiting for Rusty's response on whether we can just throw the name 'mpd' out and use 'mpd.py' for the Fedora package. That'll be easier.
-- Pavan
Rob Ross wrote:
pmpd, p is for python. On Mar 29, 2009, at 10:17 PM, Pavan Balaji wrote:
Ah, never mind. I had some conversation with Deji and he had pointed out that this is a problem with rpm -ql, that it doesn't
show the alternative name. If you do an "mpicc -show", it should
show the correct version (mpicc should be a link to the appropriate package's mpicc).
For mpd, we can't use the same technique, since the mpd music player also needs to be "alternatives capable" for that. So, we'll
need to coordinate with the author of that package for it. It's just easier to either change the name or use a different process
manager.
-- Pavan
Anthony Chan wrote:
No. /home/chan> rpm -q openmpi package openmpi is not installed ----- "Pavan Balaji" <[email protected]> wrote:
Do you already have Open MPI installed on your system?
-- Pavan
Anthony Chan wrote:
I just did a yum search for mpich2
[root@localhost proc]# yum search mpich2 Loaded plugins: refresh-packagekit =============================== Matched: mpich2 ================================ mpich2.i386 : An implementation of MPI mpich2-devel.i386 : Development files for mpich2 mpich2-libs.i386 : Libraries and configuration files for mpich2
So I installed all 3 rpms through yum and notice:
/home/chan> rpm -ql mpich2-devel /usr/bin/mp32-mpicc /usr/bin/mp32-mpicxx /usr/bin/mp32-mpif77 /usr/bin/mp32-mpif90
So all MPI compiler wrappers are prefixed with mp32-. Just to be consistent, mpd could be prefixed with mp32-. (But I don't like any of MPI compiler wrapper prefixed with mp32-) All mpich2's headers are installed in /usr/include/mpich2/. That explains how mpich2 isn't conflicting with openmpi. Also, jumpshot does not work in the
rpm, because it uses GNU's broken JVM. Could you ask Deji to make
sure it uses openjdk or sun's jdk.... ?
PS. Not sure if this is going to be happened to Deji's version...
A.Chan
----- "Pavan Balaji" <[email protected]> wrote:
Did Deji say that we are the only binary package for MPI on fedora ?
Yup. I can try to find his original email, but it was something along the lines of packages have ranks, and MPICH2 is rank 1 currently since there's no other MPI package in there.
-- Pavan
-- Pavan Balaji http://www.mcs.anl.gov/~balaji -- Pavan Balaji http://www.mcs.anl.gov/~balaji
-- Pavan Balaji http://www.mcs.anl.gov/~balaji
-- Pavan Balaji http://www.mcs.anl.gov/~balaji
mpdboot starts mpd as a daemon. doing "mpd &" does not run it as a daemon. I cannot say what most users generally do. On MonMar 30, at Mon Mar 30 6:43PM, Anthony Chan wrote:
In terms of documentation, one option is that we can de-emphasize the use of mpd.py(or mpd, pmpd, mpddaemon or mpdd) altogether, instead we recommend users to use "mpdboot -n 1" instead of "mpd.py &" to minimize the jolt to users. (Ralph, is "mpdboot -n 1" works as well as "mpd &" ?)
Since the music player can be installed before or after mpich2, we are stuck to resolve the name conflict issue.
A.Chan
----- "Rusty Lusk" <[email protected]> wrote:
Ralph and I think we are OK with mpd.py, but doesn't this invalidate
tons of documentation? Perhaps better would be "mpddaemon" or "mpdd",
to remain parallel to the other mpd-related executables like mpdcheck,
mpdtrace, etc. Even then, changing things would be quite a jolt for
users. Could there be an option to rename mpdd to mpd if you aren't
using the music player? Perhaps I don't completely understand the problem.
On Sunday,Mar 29, 2009, at 10:25 PM, Pavan Balaji wrote:
I'm actually waiting for Rusty's response on whether we can just throw the name 'mpd' out and use 'mpd.py' for the Fedora package. That'll be easier.
-- Pavan
Rob Ross wrote:
pmpd, p is for python. On Mar 29, 2009, at 10:17 PM, Pavan Balaji wrote:
Ah, never mind. I had some conversation with Deji and he had pointed out that this is a problem with rpm -ql, that it doesn't
show the alternative name. If you do an "mpicc -show", it should
show the correct version (mpicc should be a link to the appropriate package's mpicc).
For mpd, we can't use the same technique, since the mpd music player also needs to be "alternatives capable" for that. So, we'll
need to coordinate with the author of that package for it. It's just easier to either change the name or use a different process
manager.
-- Pavan
Anthony Chan wrote:
No. /home/chan> rpm -q openmpi package openmpi is not installed ----- "Pavan Balaji" <[email protected]> wrote:
Do you already have Open MPI installed on your system?
-- Pavan
Anthony Chan wrote:
I just did a yum search for mpich2
[root@localhost proc]# yum search mpich2 Loaded plugins: refresh-packagekit =============================== Matched: mpich2 ================================ mpich2.i386 : An implementation of MPI mpich2-devel.i386 : Development files for mpich2 mpich2-libs.i386 : Libraries and configuration files for mpich2
So I installed all 3 rpms through yum and notice:
/home/chan> rpm -ql mpich2-devel /usr/bin/mp32-mpicc /usr/bin/mp32-mpicxx /usr/bin/mp32-mpif77 /usr/bin/mp32-mpif90
So all MPI compiler wrappers are prefixed with mp32-. Just to be consistent, mpd could be prefixed with mp32-. (But I don't like any of MPI compiler wrapper prefixed with mp32-) All mpich2's headers are installed in /usr/include/mpich2/. That explains how mpich2 isn't conflicting with openmpi. Also, jumpshot does not work in the
rpm, because it uses GNU's broken JVM. Could you ask Deji to make
sure it uses openjdk or sun's jdk.... ?
PS. Not sure if this is going to be happened to Deji's version...
A.Chan
----- "Pavan Balaji" <[email protected]> wrote:
Did Deji say that we are the only binary package for MPI on fedora ?
Yup. I can try to find his original email, but it was something along the lines of packages have ranks, and MPICH2 is rank 1 currently since there's no other MPI package in there.
-- Pavan
-- Pavan Balaji http://www.mcs.anl.gov/~balaji -- Pavan Balaji http://www.mcs.anl.gov/~balaji
-- Pavan Balaji http://www.mcs.anl.gov/~balaji
-- Pavan Balaji http://www.mcs.anl.gov/~balaji
participants (2)
-
Anthony Chan -
Ralph Butler