LDAP server gone -> impossible to login locally!
doconnor at gsoft.com.au
Wed Sep 23 09:48:17 UTC 2009
On Wed, 23 Sep 2009, O. Hartmann wrote:
> Daniel O'Connor wrote:
> > On Wed, 23 Sep 2009, Erik Norgaard wrote:
> >> This sounds like the correct solution, AFAIK it's the same concept
> >> as for NIS, first check local files, then ldap. You don't want
> >> your root credentials possibly be leaked accross the network. On
> >> the other hand you don't want or need user accounts in the local
> >> files.
> >> Default first check local files which is fast, then fall back on
> >> ldap if the user is not found.
> > Actually I wrote them the wrong way, how odd!
> > I actually have..
> > group: cache ldap files
> > passwd: cache ldap files
> I had issues with the order
> 'files ldap'
> too, that's why I choosed 'ldap files'.
Can you remember any details why? I can't :)
> > On a related note, why is slapd so damn fragile? It's a righteous
> > pain in the bum the way you have to run db_recover-X.Y
> > /var/db/openldap-data if slapd fails to start.
> Yes, this is a lot of pain. I have had issues the same way and never
> figured out what the reason was. /var/ is very often corrupted after
> a crash, power failure or unclean reboot. Maybe not slpad is that
> fragile, but db47 is.
Yes, although openldap's handling of a bad DB is quite poor IMO.. That
said I haven't had the nerve to look at the code.
I had a quick look to see if there was a more robust looking backend but
nothing jumped out at me.
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 188 bytes
Desc: This is a digitally signed message part.
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20090923/2f40101f/attachment.pgp
More information about the freebsd-current