Hi Phil,
I am not sure how this helps. For
example ... I have my OS pointing to
lam-6.3.1, and when I try this to point
to lam-6.5.6, the hboot is still from
lam-6.3.1. My simple script is:
#! /bin/sh
export LAMHOME=/opt/local/lam-6.5.6
/usr/bin/env LAMHOME=/opt/local/lam-6.5.6
$LAMHOME/bin/lamboot -d -v hosts
BTW - I did not have any LAM daemons running,
and I cleaned /tmp/lam* before making the
test, so there were no conflicts.
So ... I would really like to set the
path to "hboot" when I call lamboot.
Joe
Phil Ehrens wrote:
>The 'env' command is your friend:
>
>/usr/bin/env LAMHOME=/some/place /some/place/lamboot
>
>A useful variation:
>
>/usr/bin/env LD_PRELOAD= LAMHOME=/some/place /some/place/lamboot
>
>Joe Griffin wrote:
>
>
>>Hello,
>>
>>Is there a way to pass the
>>path of "hboot" into lamboot?
>>
>>I have different software using
>>different versions of LAM. I
>>would like to allow users to
>>run each software package at
>>the same time.
>>
>>Currently I have to:
>>- set LAMHOME/PATH/LD_LIBRARY_PATH
>>- run job using LAM-6.3.1
>>- set LAMHOME/PATH/LD_LIBRARY_PATH
>>- run job using LAM-6.5.6
>>
>>I have control of the application scripts
>>and can have the correct "lamboot" used,
>>however, it appears that lamboot calls
>>the hboot in my path (which can only
>>be for a specific version).
>>
>>I tried creating a /bin/hboot which
>>could determine the version (new version
>>has a -b), and then call the correct
>>hboot, but that lamboot did not like
>>my trickery.
>>
>>So .. Is there a way to pass the path of
>>"hboot" to lamboot?
>>
>>Thanks,
>>Joe Griffin
>>
>>_______________________________________________
>>This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>>
>>
>
>
>
|
