Your message dated Sat, 12 Sep 2009 15:45:13 -0700
with message-id <[email protected]>
and subject line Re: Confusing messages when including non existing file
has caused the Debian Bug report #445742,
regarding Confusing messages when including non existing file
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.)
--
445742: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=445742
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libpam0g
Version: 0.99.7.1-5
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi
while trying to set up keyring support using PAM, I wrongly named one
file and PAM could not include it. However besides message that it can
not open file /etc/pam.d/common-pamkeyring, it produced bunch of
messages about "<*unknown module path*>" and "null", which look bogus to me:
PAM _pam_load_conf_file: unable to open /etc/pam.d/common-pamkeyring
PAM unable to dlopen(<*unknown module path*>)
PAM [error: <*unknown module path*>: cannot open shared object file: No such
file or directory]
PAM adding faulty module: <*unknown module path*>
PAM error loading (null)
PAM _pam_init_handlers: error reading /etc/pam.d/login
PAM _pam_init_handlers: [Critical error - immediate abort]
PAM error reading PAM configuration file
PAM pam_start: failed to initialize handlers
Couldn't initialize PAM: Critical error - immediate abort
- --
Michal Čihař | http://cihar.com | http://blog.cihar.com
- -- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.22-2-686 (SMP w/1 CPU core)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libpam0g depends on:
ii debconf [debconf-2.0] 1.5.14 Debian configuration management sy
ii libc6 2.6.1-5 GNU C Library: Shared libraries
ii libpam-runtime 0.99.7.1-5 Runtime support for the PAM librar
libpam0g recommends no packages.
- -- debconf information:
* libpam0g/restart-services: gdm exim4 cupsys cron atd
libpam0g/xdm-needs-restart:
libpam0g/restart-failed:
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHCb+E3DVS6DbnVgQRAsyTAJ9Uo3mOUdjY6Unwo3TA/x1XEVDT+QCg1wxJ
uMHRC6zTOfAi2n0lhbH4Jio=
=xMDw
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Version: 1.0.1-5
With current versions of PAM, I see the following output instead:
PAM _pam_load_conf_file: unable to open /etc/pam.d/common-nonexisting
PAM error loading (null)
PAM _pam_init_handlers: error reading /etc/pam.d/sudo
PAM _pam_init_handlers: [Critical error - immediate abort]
PAM error reading PAM configuration file
PAM pam_start: failed to initialize handlers
So I think this has been fixed upstream, probably in the lenny version.
Thanks,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
[email protected] [email protected]
signature.asc
Description: Digital signature
--- End Message ---
