From owner-freebsd-current Tue Jul 1 16:49:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA00826 for current-outgoing; Tue, 1 Jul 1997 16:49:59 -0700 (PDT) Received: from shell.uniserve.com (tom@shell.uniserve.com [204.244.210.252]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA00821 for ; Tue, 1 Jul 1997 16:49:55 -0700 (PDT) Received: from localhost (tom@localhost) by shell.uniserve.com (8.8.5/8.8.5) with SMTP id QAA28474; Tue, 1 Jul 1997 16:45:39 -0700 (PDT) X-Authentication-Warning: shell.uniserve.com: tom owned process doing -bs Date: Tue, 1 Jul 1997 16:45:39 -0700 (PDT) From: Tom To: Terry Lambert cc: current@FreeBSD.ORG Subject: Re: LDAP update In-Reply-To: <199707012257.PAA05255@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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