Hi Jeff,
I wan't clear with my last email. It is seeing LAMRSH as my new
wrapper script. Within the little error script it generates and the
various debug messages it shows that it recognizes the new LAMRSH
setting. What I was saying is that the result is no different when I
point LAMRSH at my little wrapper script as opposed to setting LAMRSH
at ssh (or not defining LAMRSH). It is not printing out the little
echo messages I put into the wrapper script (as you suggested). It
does print out the echo messages if I execute the wrapper script
directly from the command line.
Jejo
On 7/15/05, Jeff Squyres <jsquyres_at_[hidden]> wrote:
> On Jul 15, 2005, at 3:36 PM, Jejo Koola wrote:
>
> > When I follow what you suggest, it does not print any messages out at
> > all. Infact, if I point LAMRSH at just any random file, the output is
> > no different than when LAMRSH=ssh. So it seems that it is never
> > actually running the program at all. lamboot -d does print out that
> > it is "attempting to execute" ssh, so is there something that can go
> > wrong between printing "attempting to execute" and actually executing
> > the program?
>
> This seems to suggest that it's not seeing the value of LAMRSH
> properly. Did you export the environment variable (I'm assuming an
> sh-flavored shell here)? Something like:
>
> $ LAMRSH=/path/to/your/wrapper
> $ export LAMRSH
> $ lamboot -d ....
>
> or, for a csh-flavored shell:
>
> % setenv LAMRSH /path/to/your/wrapper
> % lamboot -d
>
> If the output from "lamboot -d" still shows that it's running ssh
> instead of your wrapper (I can't imagine that it will, but just in
> case), then try using the boot_rsh_agent SSI parameter:
>
> lamboot -d -ssi boot_rsh_agent /path/to/your/wrapper ....
>
> --
> {+} Jeff Squyres
> {+} jsquyres_at_[hidden]
> {+} http://www.lam-mpi.org/
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
|
