[Date Prev][Date Next]
Re: objectclass attribute
- To: Mikael Grehn <firstname.lastname@example.org>
- Subject: Re: objectclass attribute
- From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
- Date: Sun, 09 Apr 2000 21:20:14 -0700
- Cc: OpenLDAP Development <openldap-devel@OpenLDAP.org>
- In-reply-to: <38E0C531.67ED34BE@envilogg.se>
- References: <email@example.com>
At 04:44 PM 3/28/00 +0200, Mikael Grehn wrote:
> thanks for the reply.
>> >Question 3:
>> > Does it matter if I start the linked list with the objectclass
>> >attributes or that 'actual' attributes themselves?
>> The returned list of attributes is unorderred sequence.
>When using ldapsearch.exe the order seems to matter.
>If I link my attribute list (sent from my server to client) with first
>attribute 'OBJECTCLASS' and several values for this type(for example)
>and continue with ordinary attributes everything works perfectly (and both
>objectclasses are 'registered') but if I divide the objectclass values onto
>several attribute nodes like:
>it fails to read more than the first objectclass(TOP).
The latter is invalid. The returned list is an unorderred sequence
of attributes consisting of a type and unorderred sequence of
>Request of comments on some other work that I'm doing:
>I am about to insert code to limit the number of clients logged in
>simulateously by counting the number of new threads
>(one for each new client) that tries to log on.
The number of threads is not equal to the number of clients.
If you want to restrict the number of clients, restrict the
number of connections.
>The value is read from
>registry when initializing daemon.
>I have also included code to shutdown OpenLDAP from a remote program using
Okay, but I don't see the need for such a program.
>The main url-listener thread is concidered the main thread and when it is
>initialized it saves its thread id in registry.
Problem is, of course, you could have multiple slapd running on a given
>The remote application reads this id (after checking that server is running
>using global event) and posts a message to OpenLDAP thread(in main thread
>loop). Thread performs ExitProcess and shutdown is performed(in a safe
>Perhaps the current idle time for each logged on client could be checked the
>Any comments or doubts about doing this?
NT specific solution should be avoided.