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

Re: Determining the next uniqe attribute value to use with an account entry

To: "Serikstad, Kevin (CCI-Atlanta)" <Kevin.Serikstad@cox.com>, openldap-software@OpenLDAP.org
Subject: Re: Determining the next uniqe attribute value to use with an account entry
From: Norbert Klasen <norbert.klasen@daasi.de>
Date: Tue, 11 Sep 2001 10:27:28 +0200
Content-disposition: inline
In-reply-to: <761A6DCECC3AD511B295009027DC773703DAB9C5@CATL0S04.corp.cox.com>
References: <761A6DCECC3AD511B295009027DC773703DAB9C5@CATL0S04.corp.cox.com>

--On Montag, 10. September 2001 23:22 -0400 "Serikstad, Kevin (CCI-Atlanta)" <Kevin.Serikstad@cox.com> wrote:

Hi All,

	Let's try this again with a different heading. Sorry.

I was wondering if anyone sees any practical problem with having an
entry store the next available values for attributes such as uidNumber
and gidNumber. In my case, I intend to use the values more as a hint
on where to start looking rather than to act as a definitive answer.


Have a look at this thread:
http://www.openldap.org/lists/openldap-software/200011/msg00255.html

--
Norbert Klasen
DAASI International GmbH                 phone: +49 7071 29 70336
Wilhelmstr. 106                          fax:   +49 7071 29 5114
72074 Tübingen                           email: norbert.klasen@daasi.de
Germany                                  web:   http://www.daasi.de

References:
- Determining the next uniqe attribute value to use with an account entry
  - From: "Serikstad, Kevin (CCI-Atlanta)" <Kevin.Serikstad@cox.com>

Prev by Date: slurpd (1.2.11) replication problem
Next by Date: writing a ssl(tls) client
Index(es):
- Chronological
- Thread