Re: commit: ldap/servers/slapd proto-slap.h syncrepl.c
by masarati＠aero.polimi.it
> Update of /repo/OpenLDAP/pkg/ldap/servers/slapd
>
> Modified Files:
> proto-slap.h 1.789 -> 1.790
> syncrepl.c 1.474 -> 1.475
>
> Log Message:
> For ITS#6152 add slapd_str2scope(), slapd_scope2bv()
These were already available as ldap_pvt_* functions.
p.
14 years, 1 month
Re: commit: ldap/servers/slapd/overlays pcache.c
by Howard Chu
ando(a)OpenLDAP.org wrote:
> Update of /repo/OpenLDAP/pkg/ldap/servers/slapd/overlays
>
> Modified Files:
> pcache.c 1.184 -> 1.185
>
> Log Message:
> expose cachedQueryURL in overlay's monitor entry (partial fulfilment of
ITS#5178; needs new register_overlay() code in back-monitor)
Hmmm, not sure exposing the actual URLs is a good idea. Why not just the
counts? Also, if there are thousands of cached queries, this could get to be
an expensive lookup.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
14 years, 1 month
Re: commit: ldap/servers/slapd/overlays pcache.c
by masarati＠aero.polimi.it
> Update of /repo/OpenLDAP/pkg/ldap/servers/slapd/overlays
>
> Modified Files:
> pcache.c 1.183 -> 1.184
>
> Log Message:
> For refresh_purge, only delete entry if ours is the last queryid on it.
> Otherwise just remove our queryid.
Howard,
I have another round of monitor-related mods to pcache. I could
successfully merge your mods with mine. Do you mind if I commit, or do
you have more to sync?
p.
14 years, 1 month
Re: commit: ldap/servers/slapd/overlays pcache.c
by Howard Chu
hyc(a)OpenLDAP.org wrote:
> Update of /repo/OpenLDAP/pkg/ldap/servers/slapd/overlays
>
> Modified Files:
> pcache.c 1.177 -> 1.178
>
> Log Message:
> ITS#6251 framework for TTR. refresh not yet implemented.
At the moment the idea for implementing refresh is to refactor
syncrepl_entry() so that we can reuse the bulk of it. (Mainly the code that
generates an appropriate Modify request based on the difference between the
local entry and the remote entry.)
Detecting renames will be trickier since the cache typically won't have any
entryUUIDs. I think we'll simply have to treat it as a Delete / Add...
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
14 years, 1 month
Re: RE24 testing for 2.4.18 (round 2)
by William Jojo
---- Original message ----
>Date: Fri, 14 Aug 2009 14:08:23 -0700
>From: Quanah Gibson-Mount <quanah(a)zimbra.com>
>Subject: Re: RE24 testing for 2.4.18 (round 2)
>To: openldap-devel(a)openldap.org
>
>--On Wednesday, August 12, 2009 5:59 PM -0700 Quanah Gibson-Mount
><quanah(a)zimbra.com> wrote:
>
>> Please test RE24.
>
>
>A few more fixes, mainly back-meta, back-monitor, and slapo-translucent.
>
I have the following in my libraries/libldap/os-ip.c:
#ifdef TCP_KEEPCNT
<<<<<<< os-ip.c
if ( setsockopt( s, SOL_SOCKET, TCP_KEEPCNT,
=======
if ( setsockopt( s, IPPROTO_TCP, TCP_KEEPCNT,
>>>>>>> 1.118.2.19
I have no idea how others are posting successes...
Bill
>--Quanah
>
>--
>
>Quanah Gibson-Mount
>Principal Software Engineer
>Zimbra, Inc
>--------------------
>Zimbra :: the leader in open source messaging and collaboration
14 years, 1 month
FAQ and ancient entries
by Quanah Gibson-Mount
In looking at our FAQ, many entries detail ancient (2.1 and earlier)
information that is completely obsolete. It would be nice to be able to
archive off the cruft so that the site is actually of more use. Thoughts
on how best to achieve this?
Some examples:
SLAPD (with LDBM database) prerequisites include suitable database support.
One of following packages can fulfill the prerequisite.
Berkeley Database from Sleepycat (http://www.sleepycat.com/)
GNU Database Manager (GDBM) from FSF (http://www.gnu.org/)
For OpenLDAP 2.1 (or later), Berkeley DB 4.1 is recommended.
SLURPD prerequisites include:
Thread support (Posix Threads and others)
SSL/TLS prerequisites:
OpenSSL 0.9.6 from http://www.openssl.org
The OpenSSL library usually needs to be patched before it will work
correctly. See this FAQ article for details:
http://www.openldap.org/faq/index.cgi?file=185 (Note about OpenSSL and
crypt())
(Answer) How do I select a suitable LDBM backend?
(Answer) How do I force LDBM to use of BerkeleyDB?
(Answer) How do I force LDBM to use of GDBM?
(Answer) Can LDBM use NDBM?
etc.
--Quanah
--
Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra :: the leader in open source messaging and collaboration
14 years, 1 month
Normalize() API: syntax of attribute value vs. syntax of asserted value?
by masarati＠aero.polimi.it
The Normalize() API (slap_mr_normalize_func) receives a Syntax* pointing
to the syntax per which it is normalizing. However, when used in
conjunction with MRA filters, it might be useful to know what syntax the
value that is being normalized conforms to, rather than for what syntax
normalization is taking place.
Note that what syntax the normalizer is normalizing for is somehow already
determined by the specific normalization function that is in use.
Also note that when the normalization of the asserted value occurs inside
an MRA filter, the normalizer receives a pointer to the original syntax of
the attribute rather than of the syntax it is normalizing for!
I think an easy solution would be to swap the behavior: pass the asserted
syntax when normalizing the asserted value, and the attribute's syntax
when normalizing the attribute value. A better solution would be to
extend the API in order to pass both.
p.
14 years, 1 month
Re: FAQ and ancient entries
by Matt Kassawara
I'd say delete it unless of historical value (e.g., UMich-related) ... can't
see why anyone would need to use it these days.
On Fri, Aug 14, 2009 at 9:44 AM, Quanah Gibson-Mount <quanah(a)zimbra.com>wrote:
> --On Thursday, August 13, 2009 12:01 PM +0100 Gavin Henry <
> ghenry(a)suretecsystems.com> wrote:
>
>
>> ----- "Michael Ströder" <michael(a)stroeder.com> wrote:
>>
>> Quanah Gibson-Mount wrote:
>>> > In looking at our FAQ, many entries detail ancient (2.1 and
>>> earlier)
>>> > information that is completely obsolete. It would be nice to be
>>> able to
>>> > archive off the cruft so that the site is actually of more use.
>>> > Thoughts on how best to achieve this?
>>>
>>> Do we really need this ancient stuff to be archived? Many snippets are
>>> not of
>>> such a good quality which would justify the effort needed to maintain
>>> an archive.
>>>
>>> Ciao, Michael.
>>>
>>
>> It's not supported by the project I think, so should be just deleted.
>>
>
> Anyone else have an opinion?
>
> --Quanah
>
> --
>
> Quanah Gibson-Mount
> Principal Software Engineer
> Zimbra, Inc
> --------------------
> Zimbra :: the leader in open source messaging and collaboration
>
>
14 years, 1 month
TLS hostname check relaxed?
by Michael Ströder
HI!
I vaguely remember that there were code changes to the hostname cert
checking when connecting via StartTLS ext.op. or LDAPS. But I'd prefer
if the default behaviour would be strict like it was.
I'm testing with RE24 libs.
Ciao, Michael.
14 years, 1 month
