Hi Steve,
Thanks for your fast reply!
Did you not get a debconf prompt when you upgraded libpam0g? Did you refuse
to let the package restart cron for you?
Yes you are right! The issue was probably due to me running it in
autoupdate without getting notified during libpamg0 upgrade. So this is
my fault, as auto-apt and unstable is not suggested way of doing things. ;-)
But maybe the package could use its standard decision in the case
debconf is not getting answered?
This triggered the debconf questioning again and all is fine.
apt-get install libpam-modules/testing
apt-get install libpam0g/testing
apt-get dist-upgrade
Best regards, Jan
Steve Langasek wrote:
On Wed, Aug 29, 2007 at 03:17:33PM +0200, Jan Rasche wrote:
I'm sorry but this Bug seems NOT fixed yet as I have 3 Servers (I know
this is not suggested ;-)) already on this version of PAM under todays
Debian GNU/Linux unstable having still this errors.
Aug 29 15:00:01 foo CRON[9890]: PAM adding faulty module:
/lib/security/pam_env.so
Aug 29 15:00:01 foo CRON[9890]: PAM unable to
dlopen(/lib/security/pam_limits.so)
Aug 29 15:00:01 foo CRON[9890]: 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]
Did you not get a debconf prompt when you upgraded libpam0g? Did you refuse
to let the package restart cron for you?
This bug *is* fixed, using well-tested code taken from the openssl package.
(It seems the binary package is missing a dependency on debconf, but this is
fixed now in svn and if this had been the cause of your problem you would
have seen a failure at install time.) I'm sorry, but this package is
already doing everything it reasonably can to ensure cron gets restarted on
upgrade, so if it didn't happen for you, you appear to have done something
atypical and unsupported.
--
--
http://www.heise.de/tp/r4/html/result.xhtml?url=/tp/r4/artikel/25/25046/1.html&words=Sch%E4uble&T=Sch%E4uble
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
