Date: Tue, 24 Nov 1998 11:24:26 -0800 (PST) From: John Polstra <jdp@polstra.com> To: hasty@rah.star-gate.com Cc: current@FreeBSD.ORG Subject: Re: pam can't open module error messages Message-ID: <199811241924.LAA00714@vashon.polstra.com> In-Reply-To: <199811240622.WAA00757@rah.star-gate.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <199811240622.WAA00757@rah.star-gate.com>,
Amancio Hasty <hasty@rah.star-gate.com> wrote:
>
> I am getting the following error messages every time I log in to the system
> with a recent -current....
>
> Amancio
>
>
>
> Nov 23 22:10:07 cioloco login: [dlerror: Cannot open
> "/usr/lib/pam_cracklib.so"]
> Nov 23 22:10:07 cioloco login: adding faulty module: /usr/lib/pam_cracklib.so
> Nov 23 22:10:07 cioloco login: unable to dlopen(/usr/lib/pam_deny.so)
> Nov 23 22:10:07 cioloco login: [dlerror: Cannot open "/usr/lib/pam_deny.so"]
> Nov 23 22:10:07 cioloco login: adding faulty module: /usr/lib/pam_deny.so
> Nov 23 22:10:07 cioloco login: unable to dlopen(/usr/lib/pam_warn.so)
> Nov 23 22:10:07 cioloco login: [dlerror: Cannot open "/usr/lib/pam_warn.so"]
> Nov 23 22:10:07 cioloco login: adding faulty module: /usr/lib/pam_warn.so
> Nov 23 22:10:07 cioloco login: auth_pam: Module is unknown
It looks to me like you have a bogus "/etc/pam.conf" file, or else a
bogus directory "/etc/pam.d". I bet it's the latter. Delete the
directory if you have one. Where did it come from? That's the
question.
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Nobody ever went broke underestimating the taste of the American public."
-- H. L. Mencken
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199811241924.LAA00714>