On Monday 13 November 2006 16:12, Alexander Skwar wrote: > Nov 13 14:56:01 dewup-ww02 cron[5469]: PAM adding faulty module: > /lib/security/pam_unix.so Nov 13 14:56:01 dewup-ww02 cron[5469]: PAM > unable to dlopen(/lib/security/pam_limits.so) Nov 13 14:56:01 > dewup-ww02 cron[5469]: PAM [dlerror: /lib/security/pam_limits.so: > symbol pam_syslog, version LIBPAM_EXTENSION_1.0 not defined in file > libpam.so.0 with link time reference] > Nov 13 14:56:01 dewup-ww02 cron[5469]: PAM adding faulty module: > /lib/security/pam_limits.so Nov 13 14:56:01 dewup-ww02 cron[5469]: > Module is unknown > > sudo also doesn't work anymore. > > Anyone else experiencing these problems?
Yes, I ran into this when my e17 session's screensaver kicked in and it wanted a password. I could start a new X server and it would work properly, new console sessions on a vt worked fine, but the open one wouldn't authenticate me. Closing that session and starting a new was all I could do, so I have to assume the upgrade from pam-0.78-r5 to 0.99.6.3-r1 unlinked some pam stuff that the running entrance was still wanting to use. Strange that, I was under the impression that files are only fully unlinked once the last running process using it releases it. alan -- gentoo-user@gentoo.org mailing list
