From: Lorenzo Marussi <lorenzo@auroracomputers.it>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] PAM issues
Date: Mon, 13 Nov 2006 19:15:51 +0100 [thread overview]
Message-ID: <1163441751.2224.26.camel@localhost> (raw)
In-Reply-To: <45587D49.2050806@mid.message-center.info>
[-- Attachment #1: Type: text/plain, Size: 2332 bytes --]
try to make:
revdep-rebuild -p -i
and post the output.
Lorenzo Marussi
Il giorno lun, 13/11/2006 alle 15.12 +0100, Alexander Skwar ha scritto:
> Hi!
>
> Today I updated pam:
>
> [ebuild R ] sys-libs/pam-0.99.6.3-r1 USE="nls (-selinux) -vim-syntax" 0 kB
>
> Since then, I get the following errors in syslog:
>
> ==> ./cron.log <==
> Nov 13 14:56:01 dewup-ww02 cron[5467]: PAM unable to dlopen(/lib/security/pam_unix.so)
> Nov 13 14:56:01 dewup-ww02 cron[5467]: PAM [dlerror: /lib/security/pam_unix.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[5467]: PAM adding faulty module: /lib/security/pam_unix.so
> Nov 13 14:56:01 dewup-ww02 cron[5467]: PAM unable to dlopen(/lib/security/pam_limits.so)
> Nov 13 14:56:01 dewup-ww02 cron[5467]: 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[5467]: PAM adding faulty module: /lib/security/pam_limits.so
> Nov 13 14:56:01 dewup-ww02 cron[5467]: Module is unknown
> Nov 13 14:56:01 dewup-ww02 cron[5469]: PAM unable to dlopen(/lib/security/pam_unix.so)
> Nov 13 14:56:01 dewup-ww02 cron[5469]: PAM [dlerror: /lib/security/pam_unix.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_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?
>
> FWIW: I reported this also as a bug. See <http://bugs.gentoo.org/show_bug.cgi?id=155014>.
>
> Cheers,
> Alexander Skwar
> --
> I tell ya, I was an ugly kid. I was so ugly that my dad kept the kid's
> picture that came with the wallet he bought.
> -- Rodney Dangerfield
[-- Attachment #2: Type: text/html, Size: 3587 bytes --]
next prev parent reply other threads:[~2006-11-13 18:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-13 14:12 [gentoo-user] PAM issues Alexander Skwar
2006-11-13 18:15 ` Lorenzo Marussi [this message]
2006-11-13 18:20 ` Lorenzo Marussi
2006-11-13 19:14 ` [gentoo-user] " Alexander Skwar
2006-11-14 12:04 ` Alexander Skwar
2006-11-14 12:56 ` Alan McKinnon
2006-11-14 13:23 ` Alexander Skwar
2006-11-14 13:36 ` Alan McKinnon
2006-11-14 16:40 ` [gentoo-user] " Alexander Skwar
2006-11-14 17:11 ` Lorenzo Marussi
2006-11-14 19:20 ` [gentoo-user] " Alexander Skwar
2006-11-15 10:35 ` [gentoo-user] " Alexander Skwar
2006-11-14 7:52 ` [gentoo-user] " Alan McKinnon
-- strict thread matches above, loose matches on Subject: below --
2006-11-13 14:02 Alexander Skwar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1163441751.2224.26.camel@localhost \
--to=lorenzo@auroracomputers.it \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox