Thank you very much for a quick and exact reply!
Should the disk mapping be done in the LAM-7.1.4 (lam-bhost) or by CYGWIN?
Should the path at the remote nodes identify the host-path (how do I specify the host in the remote PC path)?
In the meantime I copy the xxx-mpi.exe file to the remote nodes and run my lamboot and mpirun script file!
Regards
PBSolibakke
Associate Professor dr.oecon P.B.Solibakke
Molde University College
Phone: +4790035606 ; fax: +4794760843
E-mail: per.b.solibakke_at_[hidden]
________________________________
Fra: lam-bounces_at_[hidden] på vegne av Tim Prince
Sendt: ti 23.09.2008 14:51
Til: General LAM/MPI mailing list
Emne: Re: LAM: Cygwin + LAM/MPI 2 C++
Solibakke Per Bjarte wrote:
> The problem is using the mpirun cammand on several homogenous CYGWIN-installed machines each with 1 processor (dual-core)!
> The n0 (host) work fine alone using c0 and c1.
>
> However extending the mpirun command with c2 and c3 for example, I receive the following reply from the n1 computer:
> mpirun: cannot start /cygdrive/c...../xxx_run on n1: No such file or directory
>
> A solution: If I copy the xxx_run program to the n1 computer, the application works fine.
> But shoudn't it all be on the n0 computer and the n1 computer should only be using its RAM/CPU?
>
> For the moment I use the folloing mpirun options with sucess
> mpirun -v -O -D c0 c1 xxx_run
>
> If I use the folloing mpirun options
> mpirun -v -O -D c0 c1 c2 c3 xxx_run
> the program does not execute on the n1 computer and message above appears!
>
You have made remarkable progress running lam/mpi under cygwin. In order
for a single copy of your executable to run on multiple nodes, the disk
where it is stored must be mapped to each node, and the appropriate PATH
must be set on each node. The alternative of copying the executable to
each node is OK.
_______________________________________________
This list is archived at http://www.lam-mpi.org/MailArchives/lam/
|
