mpiexec problem.

[Garrick Staples]

On Thu, Jun 21, 2007 at 01:56:51PM -0400, Pete Wyckoff alleged:
> 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.

Considered *not* having a default?  Have configure bailout if a default
isn't specified?

-- 
Garrick Staples, GNU/Linux HPCC SysAdmin
University of Southern California

Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://email.osc.edu/pipermail/mpiexec/attachments/20070621/05e38f8a/attachment.bin