On 23/02/07 23:41, Michael Mansour wrote: > 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). Probably the last would be the best. Other service-specific PAM config file (under /etc/pam.d/) use something like /lib/security/$ISA/pam_rootok.so and the $ISA part gets expanded differently on 32bit and on 64bit (this is not a shell variable). So would suggest to change /etc/pam.d/proftpd to use $ISA for a test and then file this with the upstream author... Regards jan > > Thanks. > > Michael.