Hi Jeff,
>On Wed, 23 Apr 2003, Irv Elshoff wrote:
>
>
>>Specifically, when lamboot (and recon) starts a daemon on a remote host
>>it does not provide any information in the shell variable environment to
>>indicate that LAM is starting.
>>
>Nope -- honestly, you're the first one to ask in such detail. :-)
>
>We have always treated info that comes out on stderr as an error that
>should be fixed.
>
>
The problem is NOT stderr, but more general. If LAM wants to run user
dot profiles it should provide a hint, hook or whatever so that
subsequent code can anticipate LAM (e.g., by piping stderr to /dev/null
in an exec).
>I see two options -- both of which are far too late for LAM 7.0...
>
>1. Add an option to all the "boot" commands (...) that makes LAM ignore anything on stderr and not treat it
>as an error.
>
That would probably be nice, but is not sufficient to solve my problem.
>2. Add an ability ... to
>specify a command line option to insert either a standard environment
>variable that the remote rsh/ssh target can see in their environment.
>
>I'm kinda leading towards #1.
>
Options one and two are independent as far as I can tell.
As for the 7.0 release, I'm sorry I'm too late, but adding an
appropriately named exported standard envar to the boot commands (e.g.,
LAM_MPI) seems innocent. Again, the value is not important (maybe
later), just the definition is enough to leverage lots of software.
Maybe in 7.0.1, pretty please :-)
Cheer,
Irv Elshoff.
|
