Hello Steve,
I'm sorry not really - but I may go after it later on.
Steve Langasek wrote:
Ok, this is exactly what it should show; this means that libpam0g detected
cron as a service to be restarted, and attempted to restart it, but based on
your log output cron didn't really get restarted for some reason.
Do you have logs from the automatic upgrade showing the output from
libpam0g's maintainer script?
I downgraded today.
dpkg -l | grep pam
ii libpam-modules 0.79-4 Pluggable
Authentication Modules for PAM
ii libpam-runtime 0.79-4 Runtime
support for the PAM library
ii libpam0g 0.79-4
Pluggable Authentication Modules library
Than it was auto upgraded via cron.
dpkg -l | grep pam
ii libpam-modules 0.99.7.1-3 Pluggable
Authentication Modules for PAM
ii libpam-runtime 0.99.7.1-3 Runtime
support for the PAM library
ii libpam0g 0.99.7.1-3
Pluggable Authentication Modules library
This time it looks good in syslog.
Aug 31 12:05:01 foobar /USR/SBIN/CRON[5345]: (root) CMD (if [ -x
/etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update
7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then
/etc/munin/plugins/apt update 7200 12 >/dev/null; fi)
debconf-show libpam0g
* libpam0g/restart-services:
libpam0g/restart-failed:
Regards, Jan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
