Each of the boot modules in LAM detects its own particular environment.
In particular, the SLURM and Torque resource managers set sentinel
environment variables. For example, the "tm" boot module will see the
environment variables and say "Ah ha! I'm running under Open PBS / PBS
Pro / Torque!" and will therefore activate itself (and use the TM
spawning mechanism, etc.).
That is, each module will do its own auto-detection, and if it detects
its "happy" environment, will use its own launch mechanisms.
> -----Original Message-----
> From: lam-bounces_at_[hidden]
> [mailto:lam-bounces_at_[hidden]] On Behalf Of Dennis van Dok
> Sent: Thursday, July 13, 2006 3:42 AM
> To: General LAM/MPI mailing list
> Subject: Re: LAM: LD_LIBRARY_PATH for lamd
>
> Jeff Squyres (jsquyres) wrote:
>
> >Which scheduler are you using?
> >
> >If you're not using the rsh/ssh starter for LAM, at least
> some of these
> >issues go away. For example, if you're using SLURM or Torque, your
> >local environment will be replicated on the remote nodes
> (i.e., no need
> >to tweak shell startup files such as .bashrc, $HOME/.ssh/environment,
> >etc.).
> >
> >
> I'm curious about how this works; could you explain? How does lamboot
> detect it's being run under Torque, and how does it connect
> to the other
> nodes?
>
> TIA,
>
> Dennis
>
> --
> D.H. van Dok :: Software Engineer :: www.nikhef.nl :: www.vl-e.nl
>
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
|
