Hmmmm....okay, I can see that. Are you looking for an mca param that specifies a file that might contain config info we should read when starting up the orted? What would this local configuration file look like (e.g., what kind of config directives would you need/want), would you provide it on the node where mpirun is or would it be on every remote node, etc?

All things are doable - the devil is in defining the details. :-)

On Apr 16, 2009, at 8:23 AM, Jerome BENOIT wrote:

Hi !

thanks for the reply.

On a homeless workers cluster when the workers programs are spawned via MPI_Comm_spaw{,multiple}, it would be nice to set up a default alternative assumed current which is local (rather than global as $HOME) via a local configuration file: you can play with the wdir in MPI_Info only
if the cluster is homogeneous enough.

hth,
Jerome

Ralph Castain wrote:
Not currently - could be done if there is a strong enough reason to do so. Generally, though, the -wdir option seems to do the same thing. Is there a problem with it, or some need it doesn't satisfy?
On Apr 15, 2009, at 11:00 PM, Jerome BENOIT wrote:
Hello List,

in FAQ Running MPI jobs, point 12, we read:

-wdir <directory>: Set the working directory of the started applications.
If not supplied, the current working directory is assumed
(or $HOME, if the current working directory does not exist on all nodes).

Is there a way to configure the default alternative assumed current directory (here $HOME) ?
Thanks in advance,
Jerome
_______________________________________________
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users

_______________________________________________
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users

Reply via email to