[Fedora-directory-users] LD_LIBRARY_PATH question

[Richard Megginson]

Philip Kime wrote:
> I've just build an LDAP dev server, the same as my prod servers. 
> However, I can't start the console via HTTPS under X (no problems 
> under windows). I have the same libraries etc. on my dev box (copied 
> from PROD, where it works, in fact). I get the "libnss3.s0 not found". 
> This library is certainly in /opt/fedora-ds/shared/lib, where 
> LD_LIBRARY_PATH points to in startconsole. I found out why it works on 
> PROD but not on DEV - this is because /usr/lib/libnss3.s0 exists on 
> PROD but not on DEV. HOWEVER - why is it looking in /usr/lib when 
> LD_LIBRARY_PATH is set to look in /opt/fedora-ds/shared/lib? Here is 
> the output on PROD, where it works:
Wow.  This is really strange.  When I do the same thing on my FDS 1.0.2 
installation on FC5, LD_LIBRARY_PATH works.  Are you sure you exported 
LD_LIBRARY_PATH?  Try this:
[root at hqldap01 ~]#  LD_LIBRARY_PATH=/opt/fedora-ds/shared/lib ldd 
/opt/fedora-ds/lib/libjss3.so
>  
> [root at hqldap01 ~]# echo $LD_LIBRARY_PATH
> /opt/fedora-ds/shared/lib
> [root at hqldap01 ~]# ldd /opt/fedora-ds/lib/libjss3.so
>         linux-gate.so.1 =>  (0xffffe000)
>         libnss3.so => /usr/lib/libnss3.so (0xf7f48000)
>         libsmime3.so => /usr/lib/libsmime3.so (0xf7f28000)
>         libssl3.so => /usr/lib/libssl3.so (0xf7f08000)
>         libplc4.so => /usr/lib/libplc4.so (0xf7f04000)
>         libplds4.so => /usr/lib/libplds4.so (0xf7f01000)
>         libnspr4.so => /usr/lib/libnspr4.so (0xf7ed0000)
>         libjvm.so => not found
>         libjava.so => not found
>         libc.so.6 => /lib/tls/libc.so.6 (0xf7da5000)
>         libsoftokn3.so => /usr/lib/libsoftokn3.so (0xf7d3f000)
>         libpthread.so.0 => /lib/tls/libpthread.so.0 (0xf7d2d000)
>         libdl.so.2 => /lib/libdl.so.2 (0xf7d28000)
>         /lib/ld-linux.so.2 (0x56555000)
> This upsets me as I assumed that it was using the nice new libnss3 
> etc. libs from the fedora tree. LD_LIBRARY_PATH seems to be doing 
> nothing at all. I can't see any SUID/SGID things in there which would 
> disable LD_LIBRARY_PATH? On DEV, it doesn't work because:
>  
> [root at ldapdev001 ~]# echo $LD_LIBRARY_PATH
> /opt/fedora-ds/shared/lib
> [root at ldapdev001 ~]# ldd /opt/fedora-ds/lib/libjss3.so
>         linux-gate.so.1 =>  (0xffffe000)
>         libnss3.so => not found
>         libsmime3.so => not found
>         libssl3.so => not found
>         libplc4.so => not found
>         libplds4.so => not found
>         libnspr4.so => not found
>         libjvm.so => not found
>         libjava.so => not found
>         libc.so.6 => /lib/tls/libc.so.6 (0xf7e4a000)
>         /lib/ld-linux.so.2 (0x56555000)
>  
> Now I'm worried that by PROD servers are using older libraries by 
> finding them in /usr/lib ...
>  
> PK
>  
>  
> --
> Philip Kime
> NOPS Systems Architect
> 310 401 0407
>  
> ------------------------------------------------------------------------
>
> --
> Fedora-directory-users mailing list
> Fedora-directory-users at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>   
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3178 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://listman.redhat.com/archives/fedora-directory-users/attachments/20060831/bf6a706c/attachment.bin>