Your message dated Wed, 30 Jul 2008 20:19:05 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#468868: libpam-pwdfile: unable to resolve symbol
has caused the Debian Bug report #468868,
regarding libpam-pwdfile: unable to resolve symbol
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
468868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468868
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: libpam-pwdfile
Version: 0.99-3
Severity: normal
Hello,
I have noticed that libpam-pwdfile outputs the following kind of messages in
/var/log/syslog:
Feb 20 01:37:01 rainbow CRON[18708]: PAM unable to resolve symbol:
pam_sm_acct_mgmt
Feb 20 01:37:01 rainbow CRON[18708]: PAM unable to resolve symbol:
pam_sm_open_session
Feb 20 01:37:01 rainbow CRON[18708]: PAM unable to resolve symbol:
pam_sm_close_session
Feb 20 01:37:01 rainbow CRON[18708]: PAM unable to resolve symbol:
pam_sm_acct_mgmt
Feb 20 01:37:01 rainbow CRON[18708]: PAM unable to resolve symbol:
pam_sm_chauthtok
Feb 20 01:37:01 rainbow CRON[18708]: PAM unable to resolve symbol:
pam_sm_open_session
Feb 20 01:37:01 rainbow CRON[18708]: PAM unable to resolve symbol:
pam_sm_close_session
hth,
Jerome
-- System Information:
Debian Release: 4.0
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-amd64-rainbow-master
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Versions of packages libpam-pwdfile depends on:
ii libc6 2.3.6.ds1-13etch5 GNU C Library: Shared libraries
ii libpam0g 0.79-5 Pluggable Authentication Modules l
libpam-pwdfile recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Wed, Jul 30, 2008 at 07:37:31PM -0500, Greg Norris wrote:
> Unfortunately I've been unable to reproduce your issue, even after
> duplicating the pam configuration you provided, so I'm not sure what's
> going on at the moment. I'll keep trying, and let you know if anything
> useful turns up.
Never mind, I was simply looking in the wrong place... color me
embarrassed. :(
The good news is that the fix is straightforward. The pam_pwdfile.so
module only implements the "auth" type, since it's intended strictly for
authentication, so you just need to remove any corresponding entries for
account/password/session.
signature.asc
Description: Digital signature
--- End Message ---
