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

Re: NEXTID (again!)

To: Randy Kunkee <kunkee@pluto.ops.NeoSoft.com>
Subject: Re: NEXTID (again!)
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Date: Thu, 12 Aug 1999 11:06:04 -0700
Cc: openldap-devel@OpenLDAP.org
In-reply-to: <199908121745.MAA14840@pluto.ops.NeoSoft.com>

At 12:45 PM 8/12/99 -0500, Randy Kunkee wrote:
>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?

This can happen when ldif2id2entry fails to create the NEXTID
file (for whatever reason) and slapd creates it on startup.

Sure would be nice if someone would eliminate the NEXTID
file (hint, hint).  This could be done by storing the
"next id" in the id2entry database under key 0 with a
value equal to next id.

Kurt

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: NEXTID (again!)
Next by Date: Re: NEXTID (again!)
Index(es):
- Chronological
- Thread