doc/userguide/user.tex.vin

25 % tools and concepts such as line labeling from mpiexec.
113 MPICH2 implements \texttt{mpiexec} and all of its standard arguments,
114 together with some extensions. See Section~\ref{sec:mpiexec-standard}
115 for standard arguments to \texttt{mpiexec} and various subsections of
116 Section~\ref{sec:mpiexec} for extensions particular to various process
170     mpiexec -n 3 ./cpi
240 \section{Running Programs with \texttt{mpiexec}}
241 \label{sec:mpiexec}
243 The MPI-2 Standard describes \texttt{mpiexec} as a suggested way to
244 run MPI programs. MPICH2 implements the \texttt{mpiexec} standard, and
247 \subsection{Standard \texttt{mpiexec}}
248 \label{sec:mpiexec-standard}
250 Here we describe the standard \texttt{mpiexec} arguments from the MPI-2
255    mpiexec -f machinefile -n 32 a.out
267    mpiexec -f machinefile -n 1 ./master : -n 32 ./slave
272 \texttt{mpiexec}.  This process will become an MPI process when it
277 \texttt{mpiexec}.
283 Some \texttt{mpiexec} arguments are specific to particular
289 \subsection{\texttt{mpiexec} Extensions for the Hydra Process Manager}
293 extensions to mpiexec can be found at
306 \subsubsection{\texttt{mpiexec} arguments for SMPD}
307 \label{sec:mpiexec-smpd}
309 \texttt{mpiexec} for smpd accepts the standard MPI-2 \texttt{mpiexec}
312     mpiexec
316     mpiexec -help2
320     mpiexec -n 10 myapp.exe
322 All options to \texttt{mpiexec}:
351   prevent \texttt{mpiexec} from prompting for user credentials.  Instead errors will
352 be printed and \texttt{mpiexec} will exit.
354   launch the root process directly from mpiexec if the host is local.
415 simply \texttt{fork}ed from the \texttt{mpiexec} process.  This process
418 routines from programs that are not started with \texttt{mpiexec}.  The
423 \subsubsection{\texttt{mpiexec} arguments for gforker}
424 \label{sec:mpiexec-forker}
426 In addition to the standard \texttt{mpiexec} command-line arguments, the
427 \texttt{gforker} \texttt{mpiexec} supports the following options:
432 \texttt{mpiexec}.
435 processes being run by \texttt{mpiexec}.
441  \texttt{mpiexec}.
457 In addition to the commandline argments, the \texttt{gforker} \texttt{mpiexec}
459 behavior of \texttt{mpiexec}:
463 \texttt{mpiexec} will terminate MPI programs that take longer than the value
467 \texttt{mpiexec} will use
500 \texttt{mpiexec} that makes use of the secure shell command (\texttt{ssh}) to
502 an illustration of how to build a version of \texttt{mpiexec} that works with
504 \texttt{mpiexec} programs described in this document.  In particular, it
507 provided by the \texttt{gforker} version of \texttt{mpiexec}.
508 However, this version of \texttt{mpiexec} can be used
531 mpiexec with the appropriate options corresponding to PBS, or (ii)
532 using the OSC mpiexec.
535 \subsubsection{OSC mpiexec}
539 utility called OSC mpiexec to launch MPICH2 jobs on PBS systems. More
541 \url{http://www.osc.edu/~pw/mpiexec}
560     totalview -a mpiexec -a -n 3 cpi
580 and enter other needed mpiexec arguments into the Additional Starter
627 \texttt{mpiexec} to specify the checkpointing library to use and
632     shell$ mpiexec -ckpointlib blcr \
640 \texttt{mpiexec}.  You can also automatically checkpoint the
641 application at regular intervals using the mpiexec option
646     shell$ mpiexec -ckpointlib blcr \
666     shell$ mpiexec -ckpointlib blcr \
697 libraries.  Then running the program through \texttt{mpiexec}
768 > mpiexec -n 4 wrong_reals
841 and the MPI job launcher, \texttt{mpiexec.exe}.  The dlls that implement
873 MPI jobs are run from a command prompt using \texttt{mpiexec.exe}.  See
874 Section~\ref{sec:extensions-smpd} on \texttt{mpiexec} for \texttt{smpd}
875 for a description of the options to \texttt{mpiexec}.