Newsgroups: comp.parallel.pvm
From: dillon@loria.fr (Eric Dillon)
Subject: Re: Para++ v1.0 starting slaves - Help
Organization: CRIN & INRIA-Lorraine - Nancy - FRANCE
Date: 9 Jan 1996 09:31:22 +0100
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Message-ID: <4ct94q$212@galois.loria.fr>


In article <4civga$7c9@nuscc.nus.sg>, eng20075@leonis.nus.sg (LAU YIN CHENG) writes:
|> Hi,
|> 	I was trying to start slaves and have the slaves pass their host
|> name to the master {using pvm_config(,,), pin and pout}.  But the slaves
|> are spawned on the master machine all the time.  Is there a way to spawn
|> the slaves on the other machines on the PVM list or this is a limitation 
|> of Para++v1.0.  I am using the p.init() function. 
|> 

Oops!
I'm really sorry for that, but it seems that we forgot to mention two methods
of the ParaProcess class within the user's guide.

You can use :
    -  setSpawnFlag(int )
    -  setSpawnWhere(char *)

to set the corresponding flags that will be used with pvm_spawn.

For example, if you want your tasks to be spread across machines, you can add

    ....
    p.setSpawnFlag(PvmHostCompl + PvmTaskHost);
    p.setSpawnWhere(".");
    ...

before 'p.init(...)' if you also want to spread other ParaProcess tasks, or
simply before 'p.start_slave(...)' calls, with the corresponding flags.

Both those flags are passed to pvm_spawn calls (refer to the pvm doc.).

Eric.


