[mpich-discuss] Do I need to run "mpd" every time before I execute "mpiexec"?

[Ken Raffenetti]

You should not have to specify hydra with the 3.0.4 release. It is the default. Can you send your config.log so we know what went wrong?

----- Original Message -----
> From: "Seungbum Koo" <doougsini at gmail.com>
> To: "Jeff Hammond" <jeff.science at gmail.com>, nrosner at gmail.com
> Cc: "MPICH" <discuss at mpich.org>
> Sent: Thursday, September 5, 2013 6:59:12 AM
> Subject: Re: [mpich-discuss] Do I need to run "mpd" every time before I execute "mpiexec"?
> 
> 
> 
> 
> 
> Wow. Thank you for the fast replies. You guys hardly sleep.
> 
> PROBLEM SOLVED. It works now.
> 
> Nicolás/ No. that can't be. It is my personal computer and I haven't
> installed MPICH so far.
> Jeff/ I saw that FAQ but didn't try --with-pm=hydra.
> 
> 
> 
> I first didn't configure MPICH with any process manager since hydra
> is set to default according to the installation guide. I
> reconfigured "--with-pm=hydra" and reinstalled. Now it is working.
> 
> 
> Once again, thank you for your interest and help.
> 
> Seungbum
> 
> 
> 
> 
> On Wed, Sep 4, 2013 at 11:14 PM, Jeff Hammond <
> jeff.science at gmail.com > wrote:
> 
> 
> 
> http://wiki.mpich.org/mpich/index.php/Frequently_Asked_Questions#Q:_I_don.27t_like_.3CWHATEVER.3E_about_mpd.2C_or_I.27m_having_a_problem_with_mpdboot.2C_can_you_fix_it.3F
> 
> 
> 
> 
> 
> 
> On Wed, Sep 4, 2013 at 11:02 PM, Nicolas Rosner < nrosner at gmail.com >
> wrote:
> 
> 
> 
> 
> Hi Seungbum,
> 
> 
> > do I need to run "mpd" every time before I run "mpiexec"?
> 
> No. You shouldn't need to run mpd at all.
> 
> From the FAQ: "The mpd process manager has many problems, as well as
> an annoying mpdboot step that is fragile and difficult to use
> correctly. The mpd process manager is deprecated at this point ..."
> 
> Perhaps when you typed "mpiexec", you were not really running the
> mpiexec binary that you had just built, but rather some other (really
> old) version that was already lying around on your system?
> 
> I'd suggest:
> running "which mpiexec" and "mpiexec --version"
> checking your $PATH
> specifying an absolute pathname to the new mpiexec binary instead
> of just "mpiexec"
> 
> Hope this helps,
> Nicolás
> _______________________________________________
> discuss mailing list discuss at mpich.org
> To manage subscription options or unsubscribe:
> https://lists.mpich.org/mailman/listinfo/discuss
> 
> 
> 
> 
> --
> Jeff Hammond
> jeff.science at gmail.com
> 
> _______________________________________________
> discuss mailing list     discuss at mpich.org
> To manage subscription options or unsubscribe:
> https://lists.mpich.org/mailman/listinfo/discuss