/etc/ld.so.conf contains all the directories that are searched for libraries. Run 'ldconfig' after you change that file to update the live library directory list. Make sure that your libssl.so is in a directory which is listed in that file. Assuming you've traced everything back to that level ok, that should sort you out I guess... K. Message: 15 From: "Mobeen Azhar" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Subject: RE: Cyrus IMAPD Date: Sun, 26 Nov 2000 15:45:50 -0600 charset="us-ascii" Reply-To: [EMAIL PROTECTED] Thanks Michael. I am a relative newbie to Linux, so please excuse me the following sounds ridiculous. I am assuming that libssl.so is a shared library that is loaded when needed by a program. Apparently IMAP.so used by the Cyrus administration program's perl script calls a function named SSL_write. This function is implemented in libssl.so. For some reason whatever magic the system uses to load the correct libraries for needed functions is breaking down, causing IMAP.so to complain that it cannot resolve SSL_write. So, I figure I have two options at this stage: 1) Figure out how to re-compile the Cyrus stuff so that IMAP.so statically links with libssl. I have no idea how to do this and I would rather not go down this road. 2) Figure out how to get the system to load libssl.so whenever something tries to call SSL_write. Actually, to figure out _why_ the system is not doing this, since I did install the latest binary openssl RPM. Could anyone please point me in the right direction? I would like to figure out why IMAP.so is unable to resolve SSL_write, although I have installed openssl from the binary RPM. How does one tell the system which shared library contains what symbol? I hope I made some sense, if not, I will be more than happy to answer any additional questions about my system configuration. Thanks in advance for any help, --Moby. _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list