-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 William Pursell wrote: > On OS X (on my box at least), the pam headers are in > /usr/include/pam rather than in /usr/include/security, > so defining USE_PAM causes the build to fail. > > Is pam support robust? I've patched the source > to compile, but I'm wondering: do many people > use screen's pam support?
I imagine most GNU/Linux installations use it. As to whether it's robust, I doubt I'd describe any part of Screen as "robust". That being said, PAM support doesn't seem like a complex thing to implement. Some say it can be complex to _configure_... - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer. GNU Maintainer: wget, screen, teseq http://micah.cowan.name/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAklk1cUACgkQ7M8hyUobTrFxaQCePgHBb+SoP5WtAUVA5XZv1kxE DzwAnisIfEUA8ZlTfd7tZhdLuWzlVcx2 =2jrV -----END PGP SIGNATURE-----
