SV: Debian/GNU Linux OMSA 5.1 package - AMD64

Brice Figureau brice+dell at daysofwonder.com
Tue Nov 28 03:21:07 CST 2006


On Mon, 2006-11-27 at 21:21 +0100, John Parnefjord wrote: 
> Nov 27 18:44:47 localhost omreport: PAM unable to
> dlopen(/lib/security/pam_unix.so)
> Nov 27 18:44:47 localhost omreport: PAM
> [dlerror: /lib/security/pam_unix.so: cannot open shared object file:
> No such file or directory]
> Nov 27 18:44:47 localhost omreport: PAM adding faulty
> module: /lib/security/pam_unix.so
> Nov 27 18:44:47 localhost omreport: PAM unable to
> dlopen(/lib/security/pam_nologin.so)
> Nov 27 18:44:47 localhost omreport: PAM
> [dlerror: /lib/security/pam_nologin.so: cannot open shared object
> file: No such file or directory]
> Nov 27 18:44:47 localhost omreport: PAM adding faulty
> module: /lib/security/pam_nologin.so
> 
> The file /lib/security/pam_nologin.so is obviously there and so is
> pam_unix.so but the lib directory is just a symlink to lib64.   

I don't know if it will help you.
What I did to overcome this issue was to install in /lib32/security all
the 32 bits pam modules I extracted from the i386 32bits libpam-module.
Unfortunately there is no lib32pam package in amd64 Etch...
It seems omsa is a 32bits application, thus it needs 32bits version of
the libs.
-- 
Brice Figureau <brice+dell at daysofwonder.com>



More information about the Linux-PowerEdge mailing list