mpiexec problem.

[Steve Young]

Pete,
	Thanks. Garrick Staples suggested on the mpich-discuss list that I
recompile with  --with-default-comm=pmi which seemed to make it work
properly. Should I be using that or specify mpich2 vs. pmi? 

-Steve

PS. While the documentation does spell this out I guess I didn't really
read it carefully enough. I'll think about it and perhaps I can come up
with some ideas for you as I bet this is a common error for people just
starting out. I think for me the hardest part was that it did appear to
be running properly. I wonder if there is a way to put something in the
code to report this problem when people try to use mpiexec. (ie. spit
out "error don't know what comm library to use"). 

On Thu, 2007-06-21 at 13:56 -0400, Pete Wyckoff wrote:
> csamuel at vpac.org wrote on Thu, 21 Jun 2007 11:52 +1000:
> > On Thu, 21 Jun 2007, Steve Young wrote:
> > > The osc mpiexec spawns 8 seperate processes while mpirun does them in
> > > parallel. Any ideas what I could try to remedy this? Thanks,
> > 
> > If you are not using Myrinet (and have not altered the build time default) 
> > then you will need to specify the correct MPICH communication lib to use.
> > 
> > Quoting the manual page:
> > 
> >        -comm type
> [..]
> > What you see is often diagnostic of someone using the default MPICH-GM support 
> > for a P4 application.
> 
> Yeah.  The magic configure option is "--with-default-comm=mpich2".
> If you have ideas about how to fix the documentation to make this
> stand out better, please let us know.
> 
> 		-- Pete