Re: nsswitch.conf and openldap-server
Olivier Thauvin <[email protected]> Wed, 8 Feb 2006 17:16:33 +0100
| Newsgroups | gmane.linux.mandrake.server |
|---|---|
| Message-ID | <[email protected]> |
--nextPart3961183.qyYUZkxUg1 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Le Mercredi 8 F=E9vrier 2006 17:02, Luca Berra a =E9crit : > On Wed, Feb 08, 2006 at 04:15:02PM +0200, Buchan Milne wrote: > >On Wednesday 08 February 2006 16:03, Frederic Bongat wrote: > >> Hi, > >> > >> I found the problem, It comes only when I get ldap on host variable : > >> > >> "host files dns ldap" in nsswitch.conf > > > >Hmm, yes, I never do this, but some people trying to use nss_wins (which > > is only useful in the hosts line) had the same problem ... > > > >Regards, > >Buchan > > strange, it should not happen if everything needed to boot the ldap > server is available in /etc/hosts. > > if not it is possible that it slows down. In the same game, recently I setup a computer using pam-pgsql, aka auth ove= r=20 postgres table, and finally to have a unique account base, postgres=20 authentify its user using pam, then pam back to postgres. The thing to avoid if of course a chicken-egg problem, aka pam needing to=20 authentify itself on postgres to access to table. The Frederic's situation isn't this one: it try to find the hostname (of=20 another one), not in /etc/hosts, no dns availlable (no network), try ldap, = to=20 find ldap host, try /etc/hosts, not in hosts, no dns, try ldap, try to find= =20 ldap host, etc... then endless loop. Just an idea... --nextPart3961183.qyYUZkxUg1 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQBD6hlhk29cDOWzfVARAuBqAKDmGXOmVARox9P+CELMPEUQTGRKJgCg8j7j XPvoL1sDD0RvUjihTsxWF4g= =w2K7 -----END PGP SIGNATURE----- --nextPart3961183.qyYUZkxUg1--