SCIENTIFIC-LINUX-USERS Archives

February 2007

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Michael Mansour <[log in to unmask]>
Reply To:
Michael Mansour <[log in to unmask]>
Date:
Sat, 24 Feb 2007 08:41:29 +1000
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
Hi,

I've got some errors on two of my SL4.4 x86_64 servers.

I'm using proftpd 1.3.1rc2 and I see errors like this in the logs:

PAM unable to dlopen(/lib/security/pam_listfile.so) 
PAM [dlerror: /lib/security/pam_listfile.so: cannot open shared object file:
No such file or directory] 
PAM adding faulty module: /lib/security/pam_listfile.so 
PAM unable to dlopen(/lib/security/pam_pwdb.so) 
PAM [dlerror: /lib/security/pam_pwdb.so: cannot open shared object file: No
such file or directory] 
PAM adding faulty module: /lib/security/pam_pwdb.so 

These files are located in /lib/security on 32bit SL, but on 64bit SL they are
located in /lib64/security.

What is the correct way to fix this?

Should I be adding the /lib64/security into the ld config paths, or creating
symbolic links in /lib/security to the correct paths, or should proftpd really
be looking for these libraries in their correction locations? (I can notify
the author if this is the case).

Thanks.

Michael.

ATOM RSS1 RSS2