From owner-freebsd-current Mon Jul 5 13:28: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from cantor.boolean.net (cantor.boolean.net [209.133.111.73]) by hub.freebsd.org (Postfix) with ESMTP id DEC9D15041 for ; Mon, 5 Jul 1999 13:27:32 -0700 (PDT) (envelope-from Kurt@OpenLDAP.Org) Received: from OpenLDAP.Org (localhost [127.0.0.1]) by cantor.boolean.net (8.9.2/8.9.1) with ESMTP id UAA92712; Mon, 5 Jul 1999 20:31:52 GMT (envelope-from Kurt@OpenLDAP.Org) Message-ID: <378112E3.A1E8635@OpenLDAP.Org> Date: Mon, 05 Jul 1999 13:17:39 -0700 From: "Kurt D. Zeilenga" Organization: OpenLDAP X-Mailer: Mozilla 4.6 [en] (WinNT; U) X-Accept-Language: en-GB,en-US,en,de-DE,de MIME-Version: 1.0 To: Amancio Hasty Cc: mtaylor@cybernet.com, freebsd-current@FreeBSD.ORG, Mark Wilcox Subject: Re: LDAPed FreeBSD References: <199907051959.MAA27212@rah.star-gate.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This discussion is diverging a bit from this list's charter. Hence, I'll be brief. Amancio Hasty wrote: > True LDAP (v2 or v3) does not provide record locking . Now the question is > does Novell's NDS 8 -- a native LDAP v3 -- , Oracle's Directory > Server or Microsoft Active Directory does if they do then how ? Commonly through other directory (or database) access mechanisms. Or, possibly, though some private or experimental LDAPv3 control or extended op they added to their client/servers (LDAPv3 is an extensible protocol). > Again my emphasis is on configuring network services or other system services > if appropiate and to provide a HTML interface which is sufficiently rich to be > user friendly. I think this would be a fine use of LDAP. Kurt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message