pam_rhosts module

["Michael K. Johnson" <johnsonm redhat com>]

When I sent in my original static patches, I inadvertantly left the
pam_rhosts module commented out, and Andrew commented on that fact
and fixed it.  I had commented it out because it didn't build, and
the error message had led me to initially assume that the module
wasn't really finished yet...  Oops...

At least with libc 5.2.13 and kernel pre2.0.6, it doesn't finish the
compile because of header file breakage from within inclusion of
resolv.h.  I finally discovered that I can build it without including
resolv.h and it seems to be happy.  I haven't tested it yet, but at
least it builds...

While looking at pam_rhosts_auth.c, I came up with a few questions:
 o Why is MAXDNAME ever defined?
 o Why is __USE_BSD defined (twice!)?  It's supposed to be a historical
   relic and not actually used anywhere in current code, as I understand
   it.
 o Why are several header files included multiple times?
 o Why is resolv.h included?  If there's no reason to include it, it
   can be removed and then will quit causing trouble...  :-)

Thanks for any answers,

michaelkjohnson

"Ever wonder why the SAME PEOPLE make up ALL the conspiracy theories?"