Hi, On Sun, Apr 15, 2007 at 09:23:31PM +0200, Frederic Schutz wrote: > > Yes, I am still able to reproduce it, and I am happy to believe that a > PAM module is responsible, but I have no idea which one -- and I am not > able to "play" too much with the configuration (this is a server in > production) in order to narrow it down, unfortunately.
If you provide the PAM configuration, we can try to reproduce it. This usually means files like: * /etc/pam.d/su * /etc/pam.d/common-auth * /etc/pam.d/common-password * /etc/pam.d/common-session * /etc/security/pam_env.conf * /etc/security/limits.conf * /etc/pam.conf Note that there may be sensible information in them (just filter out some fields if you wish). You can also check if it is caused by a file corruption: debsum login libpam0g libpam-runtime libpam-modules (and maybe other packages) Kind Regards, -- Nekral -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
