After update to new glibc some apps stops working like cron for example: Apr 29 00:40:01 [cron] PAM unable to dlopen(/lib64/security/pam_unix.so): /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /lib64/libcrypt.so.1) Looks like solution is to rebuild PAM after glibc update, but that never was a case, I dont remeber such need. I found the solution here: http://archives.gentoo.org/gentoo-user/msg_208faa222c64e107dd272c8504035a07.xml The glibc comes from arch-stable gentoo, I think someone should take care of it, such things shoudn't really happen in stable gentoo. There is no even single einfo about possible issues. Not cool. Reproducible: Always
Just restart cron, it should work just fine (given that I've not rebuilt pam myself). The problem is that you can't mix libc and libcrypt from different versions, and due to the way PAM works, this is what happens. It's not really different than the fact that you need to restart cron after updating PAM because the symbols between libpam and the pam modules can't be mixed.
