[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: NEXTID (again!)

To: h.b.furuseth@usit.uio.no (Hallvard B Furuseth)
Subject: Re: NEXTID (again!)
From: Randy Kunkee <kunkee@pluto.ops.NeoSoft.com>
Date: Thu, 12 Aug 1999 18:23:14 -0500 (CDT)
Cc: openldap-devel@OpenLDAP.org
In-reply-to: <HBF.990813ctk1@bombur.uio.no> from Hallvard B Furuseth at "Aug 13, 99 00:04:35 am"

> Randy Kunkee writes:
> > If I simply run ldif2id2entry, NEXTID gets set correctly.  But I just
> > ran an ldif2ldbm -j 10 last night, and NEXTID ended up containing "1".
> > If ldif2id2entry is not doing this, what is?
> 
> Which OpenLDAP version and ldif2ldbm.c revision?  Do you use gdbm or db
> (see LDBM_LIBS in config.status)?  back-ldbm or back-bdb2?
> 
> I believe I fixed that in -devel for back-ldbm some time ago (with
> variable ldbm_ignore_nextid_file), and someone fixed it in another way
> (by introducing SLAP_TOOLID_MODE) in back-bdb2.  So...?
> 
> -- 
> Hallvard
> 
> 
> 

Releng 1.2 current, and db-2.7.5.  Could be it just didn't get into release
engineering.  Sorry, should have mentioned that.

Randy

References:
- Re: NEXTID (again!)
  - From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>

Prev by Date: Re: NEXTID (again!)
Next by Date: Connection->c_protocol, vlv, server-side sorting.
Index(es):
- Chronological
- Thread