thats great. I have to use LAM on all nodes.
I have another problem. I am installing LAM-MPI on globus2.4
When I do
$lamboot -ssi boot globus hostfile
hostfile contains the following information:
"pod.eecs.umich.edu:/O=Grid/OU=GlobusTest/OU=simpleCA-swarm.eecs.umich.edu/OU=eecs.umich.edu/CN=John
Pod" prefix=/n/pod/z/globe/lammpi cpu=2
pod.eecs.umich.edu is configured to run gsigatekeeper as root.
I am getting the following error:
ERROR: LAM/MPI unexpectedly received the following on stderr:
GRAM Job submission failed because the gatekeeper failed to find the requested
service (error code 93)
thanks
Siva
Quoting Prashanth <pcharapa_at_[hidden]>:
>
> Hello,
>
> Yes, LAM-MPI supports spawn.
>
> But the LAM Run Time Environment must exist everywhere that you want to
> spawn. Hence, you cannot spawn to a node that you have not already
> lambooted or lamgrow'n.
>
> Hope this helps.
>
> Prashanth Charapalli,
> LAM-MPI Team.
>
> Thus spoke sbandham_at_[hidden] in the message sent on Tue, 3 Feb 2004
>
> ->Hi
> -> Does LAM/MPI on top of globus2.4 support Dynamic Process management ?
> ->ex: MPI_Comm_spawn
> ->
> ->thanks
> ->Siva
> ->_______________________________________________
> ->This list is archived at http://www.lam-mpi.org/MailArchives/lam/
> ->
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
|
