Package: libpam-runtime
Version: 1.3.1-1
Followup-For: Bug #922178

Hi:

Same thing. "/etc/init.d/cron restart" seems to get things back to
normal.

Just after upgrade:
---8<---
CRON[12874]: PAM unable to dlopen(pam_unix.so): /lib/security/pam_unix.so: 
cannot open shared object file: No such file or directory
CRON[12874]: PAM adding faulty module: pam_unix.so
CRON[12874]: Authentication failure
--->8---

After restarting cron, things work again:
---8<---
CRON[26043]: pam_unix(cron:session): session opened for user root by (uid=0)
CRON[26043]: pam_unix(cron:session): session closed for user root
--->8---

Upgrading a package should automatically restart services that depend
on it, like it happens with ssh server.

Thanks,
GSR
 

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.17.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libpam-runtime depends on:
ii  debconf [debconf-2.0]  1.5.70
ii  libpam-modules         1.3.1-1

libpam-runtime recommends no packages.

libpam-runtime suggests no packages.

-- debconf information:
  libpam-runtime/conflicts:
  libpam-runtime/title:
  libpam-runtime/override: false
* libpam-runtime/no_profiles_chosen:
  libpam-runtime/you-had-no-auth:
* libpam-runtime/profiles: unix, capability

Reply via email to