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

Re: NEXTID (again!)

To: Randy Kunkee <kunkee@pluto.ops.NeoSoft.com>
Subject: Re: NEXTID (again!)
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Date: Fri, 13 Aug 1999 00:04:35 +0200
Cc: openldap-devel@OpenLDAP.org
In-reply-to: <199908121745.MAA14840@pluto.ops.NeoSoft.com>
References: <199908121745.MAA14840@pluto.ops.NeoSoft.com>

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

Follow-Ups:
- Re: NEXTID (again!)
  - From: Randy Kunkee <kunkee@pluto.ops.NeoSoft.com>

References:
- NEXTID (again!)
  - From: Randy Kunkee <kunkee@pluto.ops.NeoSoft.com>

Prev by Date: _LIBC_REENTRANT in Linux?
Next by Date: Re: NEXTID (again!)
Index(es):
- Chronological
- Thread