Ewan MacMahon wrote:
>> [root@farm001 lib]# echo $PYTHONPATH
>> /opt/glite/lib/python:/opt/lcg/lib/python:/opt/glite/lib/python2.3/site-packages/amga
>>
>>
> That's what I see too, and that appears to be a working setup.
>
That wasn't the case for me as default. I added
/gridpath_append "PYTHONPATH" "/opt/lcg/lib/python" /
to the grid-env.sh by hand and I did that for only one WN to test. I
see, rest of my WNs (at least 20 of them) don't have "/opt/lcg" in the
PYTHONPATH.
I'm using 32-bit WN on 64-bit machine.
[root@farm001 ~]# rpm -qa | grep WN
glite-WN-3.1.19-0.i386
Confused :-\ ,
Santanu
>> I've also started seeing this at the very end every time I reconfigure
>> a WN (since last night):
>>
>> WARNING: /opt/lcg/lib64 doesn't exist. PYTHONPATH and PERL5LIB won't
>> contain 64bit libraries
>> WARNING: /opt/glite/lib64 doesn't exist. PYTHONPATH and PERL5LIB won't
>> contain 64bit libraries
>>
>> I didn't see this before. Should there a be a "lib64" in there?
>>
>>
> I'd have thought not, at least not at the moment. If you're running the
> 32 bit
> WN release on a 64 bit system there shouldn't be 64 bit libraries under
> /opt.
> However, if you were running the 64 bit WN release (which I don't think
> any of
> us actually are yet?) then I'd expect/guess/hope that it would put its
> libraries
> in lib64 directories. The YAIM scripts are probably/hopefully shared
> between
> the two releases, and I'd guess that this is just it trying to tell
> which type
> of system it's trying to configure.
>
> Ewan
>
|