Re: [gentoo-cluster] Re: eselect-mpi issues

[Eric Thibodeau <kyron@neuralbs.com>]

[-- Attachment #1: Type: text/plain, Size: 3150 bytes --]

Justin Bronder wrote:
> On 12/06/08 11:28 -0700, Bryan Green wrote:
>   
>> Hello,
>>
>> I'm beginning to give empi/eselect-mpi a try.  Bravo, Justin, for making
>> these!
>>     
>
> Thanks for trying them out, I'm hoping someone else finds them as useful as I
> have.
>   
It is planned to be part of the Gentoo Clustering LiveCD ;)
>   
>> I've run into one bug in eselect-mpi that effects csh users (a popular
>> shell where I work).  There is simply one setenv line that has bash syntax
>> rather than csh syntax.  I already submitted a bug: its bug 226105.
>> Here is the patch to fix it:
>>
>> ================================================
>> --- files/mpi.eselect-0.0.3     (revision 1137)
>> +++ files/mpi.eselect-0.0.3     (working copy)
>> @@ -161,7 +161,7 @@
>>  setenv PATH "${binpath}"
>>   setenv MANPATH "${manpath}"
>>    setenv LD_LIBRARY_PATH "${lld}"
>>    -setenv ESELECT_MPI_IMP="${1}"
>>    +setenv ESELECT_MPI_IMP "${1}"
>>     EOF
>>      
>>           echo "Remember to source ${user_ev_sh} or ${user_ev_csh}"
>> ================================================
>>     
>
> Fixed in eselect-0.0.3-r1.  Also found another mistake when setting PATH for
> c shells and fixed that as well.
>
>   
>> Also, in the README file, the for loop in step 6 is incorrect:
>>
>> for i in $(ls ${HOME}/.env.d/*); do
>>     source ${HOME}/.env.d/${i}
>> done
>>
>> Results in:
>>
>> -bash: /home/bgreen/.env.d//home/bgreen/.env.d/mpi.csh: No such file or directory
>> -bash: /home/bgreen/.env.d//home/bgreen/.env.d/mpi.sh: No such file or directoryA
>>     
>
> Also fixed.  You might also want to check out the doc I've been working on
> lately, http://dev.gentoo.org/~jsbronder/empi.xml.  Hopefully it's a little
> more up to date.
>   
Have to remember that one ;)
>   
>> On the system where I'm using empi, I've created files in /etc/profile.d to
>> source the user's .env.d files when they log in.  What do you think about
>> having the eselect-mpi ebuild install these, so mpi users dont have to do
>> that part manually?  They would instead just have to source /etc/profile or
>> /etc/csh.login after running 'eselect mpi'.
>>     
>
> Love it, I had not even thought of using this mechanism before even though I
> should have.  It will also simplify switching from an mpi environment to one
> without it.  I'll try to get something checked into the overlay soon,
> shouldn't be more than a few days.<
>   
Keep us posted because I will definitely  want that version!
>   
>> Here are my versions of the files in /etc/profile.d:
>>
>> ==============
>> mpi-config.sh
>> ==============
>> if [ -d ${HOME}/.env.d ]; then
>>     for i in ${HOME}/.env.d/*.sh ; do
>>         . "${i}"
>>     done
>>     unset i
>> fi
>>
>> ==============
>> mpi-config.csh
>> ==============
>> if ( -d ${HOME}/.env.d ) then
>>     set nonomatch
>>     foreach i ( ${HOME}/.env.d/*.csh )
>>         source ${i}
>>     end
>>     unset i nonomatch
>> endif
>>
>> ==============
>>
>> -bryan
>>     
>
> Thanks again for testing and your comments, they're much appreciated.
>   
Yeah, thanks you both, multi-mpi-on-1-system has always plagued me too ;)

[-- Attachment #2: Type: text/html, Size: 4150 bytes --]