Date: Tue, 1 Jul 1997 16:45:39 -0700 (PDT) From: Tom <tom@uniserve.com> To: Terry Lambert <terry@lambert.org> Cc: current@FreeBSD.ORG Subject: Re: LDAP update Message-ID: <Pine.BSF.3.96.970701164359.28461A-100000@shell.uniserve.com> In-Reply-To: <199707012257.PAA05255@phaeton.artisoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 1 Jul 1997, Terry Lambert wrote: > > Well, I have narrowed the LDAP problem down to a bad interaction > with the ndbm code. > > When compiled to use ndbm, an explicit flush prior to a the close > fails to write the data aout to the database files. > > The failing flush occurs in the ldif2ldbm program when it is > attempting to inialize the database, and results in zero length > database files. > > The subsequent LDAP lookups over the wire fail to obtain the > requested data. > > I went to the BSD btree code, and the problem went away. I > also went tot he BSD hash code, and the problem also went away. > > So there is a bug in ndbm, but I don't have it pegged any closer > than that. > > The LDAP server is at: > > ftp://terminator.rs.itd.umich.edu/ldap/ldap.tar.Z > > if the current ndbm maintainer is interested in tracking down > the problem. > > Use the .ps or .pdf "slapd guide", section 2 "A Quick-Start Guide > to Running slapd", pages 10 and 11. In step 7 "Create a database", > add the parameter "-d 65535" to get debug information about the > database creation. > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > FreeBSD doesn't have a ndbm. It just a ndbm compatibility module that goes over db (using hash type, I believe). Tom
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.970701164359.28461A-100000>