LAM/MPI logo

LAM/MPI General User's Mailing List Archives

  |   Home   |   Download   |   Documentation   |   FAQ   |   all just in this list

From: Luttinger, Matthew (matthew.luttinger_at_[hidden])
Date: 2008-09-17 08:42:45


I tried that also... Still no joy

-----Original Message-----
From: lam-bounces_at_[hidden] [mailto:lam-bounces_at_[hidden]] On Behalf
Of Jeff Squyres
Sent: Wednesday, September 17, 2008 8:39 AM
To: General LAM/MPI mailing list
Subject: Re: LAM: Boot_rsh_ignore_stderr

Mmm... I forget the exact semantics of how LAM's mpiexec passes
parameters to lamboot. You might want to call lamboot separately
(with "-ssi ...") and then use "mpiexec" without the -boot option.

On Sep 17, 2008, at 8:34 AM, Luttinger, Matthew wrote:

>
> I work in a classified environment, so I can not send log files with
> this question.
>
> Due to the classified environment, my Security group mandates that
> we have a security banner that gets displayed when "ssh" is executed.
>
> This banner comes over stderr, and LAM fails, but tells me I can
> "disable this behaviour (i.e. have LAM ignore output on standard
> error) in the rsh boot module by setting the SSI parameter
> boot_rsh_ignore_stderr to 1"
>
>
> I am just not sure how to insert that SSI parameter into my LAM
> scripts ?
>
>
> My script looks like :
>
> Mpiexec -boot -ssi rpi tcp -v -machinefile <my_machine_file> -
> configfile <my_config_file>
>
>
> I have tried inserting "-ssi boot_rsh_ignore_stderr 1" into the
> above command and have had no success causing LAM to ignore the
> stderr .
>
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/

-- 
Jeff Squyres
Cisco Systems
_______________________________________________
This list is archived at http://www.lam-mpi.org/MailArchives/lam/