Thanks, Fredrik! I set up the LD_LIBRARY_PATH and it works. But I am getting into another problem that the kinit couldn't reach the KDC I specified, errors are:
kinit(v5): Cannot resolve network address for KDC in requested realm while getting initial credentials However, I remember when I did this within windowsXP, leash was able to do the DNS look up once I turned on the flag in the krb5.ini. BTW, do you know where krb5.conf exists for krb5-1.3.5-sparc-solaris2.9 (MIT implementation) besides some directory such as: /etc/krb5 (default on Solaris). Thanks in advance, - Ying -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fredrik Tolf Sent: Tuesday, October 05, 2004 11:12 AM To: [EMAIL PROTECTED] Subject: Re: ld.so.1: kinit: fatal: libkrb4.so.2: open failed: No such file On Tue, 2004-10-05 at 13:15 +0000, "Ying Zhao" wrote: > I downloaded krb5-1.3.5-sparc-sun-solaris2.9.tar and unpacked the tar to > get it installed on my UNIX box. Then I tried to run kinit (the one in > the unpacked directory), I got an error: > > ld.so.1: kinit: fatal: libkrb4.so.2: open failed: No such file or > directory > > Then I checked the directory structure and found the unpacked stuff is > under $MU_CURRENT_DIR/usr/local/lib. Should this be a problem if the all > the kinit etc. are supposed to directly run under /usr/local/bin, and > libraray be under /usr/local/lib rather than build another directory > structure under my current dir? Of course, this isn't really a Kerberos error, but an error in the dynamic linker, and since I'm not sure how the dynlinker in Solaris works, I cannot guarantee the correctness of my answer. The usual POSIX dynlink behavior, however, is to first look in a few system-defined directories (on GNU/Linux, these are defined /etc/ld.so.conf -- I don't know whether that's POSIX-defined, but it doesn't seem to exist on the Solaris system I have access to), which usually include /lib, /usr/lib and /usr/local/lib, and sometimes a few others. After that, the dynlinker looks in the directories specified in the environment variable LD_LIBRARY_PATH, which, just like PATH, is a colon seperated list of directories. If you want this to work, you will probably want to add $MU_CURRENT_DIR/usr/local/lib to LD_LIBRARY_PATH (don't forget to export LD_LIBRARY_PATH if it's not already defined). Fredrik Tolf ________________________________________________ Kerberos mailing list [EMAIL PROTECTED] https://mailman.mit.edu/mailman/listinfo/kerberos ________________________________________________ Kerberos mailing list [EMAIL PROTECTED] https://mailman.mit.edu/mailman/listinfo/kerberos