-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mark Knecht wrote: > OK, knowing as you all do that I'm a non-admin sort of person these > sort of instructions - the > 2 paragraphs at the end - scare me. I hate having to guess what anyone means. > > lightning pam.d # qfile -o /etc/pam.d/* > /etc/pam.d/gdmconfig > /etc/pam.d/xdm > lightning pam.d # >
I was having the same problems earlier in the week. The solution is actually pretty simple. The output above indicates that xdm and gdmconfig aren't being used any longer - they're orphans. I just moved the files elsewhere (for temporary safe-keeping), and upgraded PAM, and there were no issues. All the files that used the obsolete functions were upgraded some time ago apparently - but if you have a system that has been upgraded year-after-year apparently there are orphan files that date WAY back... However, I agree that PAM is one of those things that everybody depends on but otherwise seems to behave like black magic for most people. I've yet to see a guide on PAM that actually makes it easy to understand. (There are TONS of guides that ATTEMPT to make it easy to understand, but every one I've seen falls far short). I considered it a major accomplishment when I was able to hack my sshd PAM config to restrict logins to a list of particular accounts... -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHLbS3G4/rWKZmVWkRArPOAJwPJuIUe8tJkacz5jmyzaImNFaTjgCdF8k/ ++g0HXiS7/ZPaUOMk6YY+OA= =q/hy -----END PGP SIGNATURE-----
smime.p7s
Description: S/MIME Cryptographic Signature
