On Nov 18, 2004, at 11:21 AM, Alexey Nikolaevich Salnikov wrote:
> Thanks! Probably im reading documentation not very thoroughly. Ask
> again.
> Have you a running mechanizm that does not use any network protocols?
I guess I'm not sure what this means... Are you asking if we fork/exec
instead of rsh/ssh, or any other back-end protocol to start jobs?
If so, yes. If you're running *only on a single node*, then lamboot
will fork/exec the daemon into the background. mpirun always sends a
message to all relevant lamd's (which, in this case, will be local),
who, in turn, fork/exec the processes in your parallel application. So
there's no traffic across any networks.
If you're running on multiple nodes, then the network *must* be
involved somehow -- either via rsh/ssh, using LoadLeveler APIs, or some
other equivalent mechanism.
> I want to run lamboot but when LAM is in booting stage it must not
> set any network connections between other machines and to localhost.
> If it
> is allowed for user to call rsh/ssh or other remote calls then after
> user
> time left LoadLeveler will not be able to finalize spawned processes
> that
> run by ssh or other remote call program.
> We intent to use LAM as simulator distributed memory over shared memory
> and use messages as a way to organize interconection between
> processors in
> SMP system.
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
