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