On Mon, Sep/24/2007 09:00:32PM, Jeff Squyres wrote:
> If the "whatami" shell script is missing and we get blank values for
> the following fields, should we error/abort the MTT client? I'm
> thinking yes... opinions?
>
> - platform_type
> - platform_hardware
> - os_name
> - os_version
>
> All of these fields are settable from the INI file (in the [MTT]
> section). The default value for them is to invoke &whatami() (with
> various arguments, which ends up invoking the "whatami" executable)
> to get the values. So most people won't need to do anything. But
> when we go to an MTT tarball that does not ship "whatami", it is
> plausible that you might get empty values for these fields without
> realizing it.
>
> Thoughts?
>
How about we first go with Plan C: uname (if it's
available).
platform_type = &shell("uname -p")
platform_hardware = &shell("uname -m")
os_name = &shell("uname -s")
os_version = &shell("uname -v")
Otherwise default to "unknown".
So the we go down this list:
1. User-specified in INI
2. whatami
3. uname
4. "unknown"
-Ethan
> --
> Jeff Squyres
> Cisco Systems
>
> _______________________________________________
> mtt-devel mailing list
> mtt-de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel
