openldap-devel

openldap-devel@openldap.org

1443 discussions

Re: commit: ldap/servers/slapd/overlays rwm.c rwm.h rwmconf.c rwmdn.c rwmmap.c
by Pierangelo Masarati 14 Jul '07

14 Jul '07

ando(a)OpenLDAP.org wrote: > Log Message: > major improvement: baseline support for back-config; minor improvement: trim code to handle absence of librewrite (enable forced when slapo-rwm is configured...) The major defect of this implementation is that there is no "rwm-map" or "rwm-rewrite*" unparse. So the input is saved "as is"; it is presented "as is" via the back-config interface, and it needs to be entirely replaced instead of fine-grain edited by inserting/deleting/resorting statements. I'll leave this as a future development if needed. I plan to work at back-relay and back-meta some time, but probably not in the very short term, so please don't wait for it for a future 2.4 release. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

Re: commit: ldap/servers/slapd backend.c
by Howard Chu 12 Jul '07

12 Jul '07

hyc(a)OpenLDAP.org wrote: > Update of /repo/OpenLDAP/pkg/ldap/servers/slapd > > Modified Files: > backend.c 1.378 -> 1.379 > > Log Message: > ITS#4986 - remove special manageDSAit handing in select_backend() Of course this makes the manageDSAit parameter to select_backend() totally unnecessary. I guess I'll remove that soon as well. -- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

ldap_dn2ad_canonical() and UTF8
by Ralf Haferkamp 11 Jul '07

11 Jul '07

Hi, The ldap_dn2ad_canonical() function is supposed to map an LDAP DN into a Active Directory Canonical Name. Does anybody know why this function disallows DNs with UTF8 characters in them? The comments in the code are somewhat uncertain regarding this ;) /* * b) does DCE/AD support UTF-8? * no clue; don't think so. */ But testing with a Windows Server showed me that is seems to be possible to have UTF characters in the Canonical name. I am asking because I'd like to commit a change that allows to have UTF8 in canonical names (by removing the check for LDAP_AVA_NONPRINTABLE from the strval2ADstr* functions. -- regards, Ralf

2 1

Re: commit: ldap/servers/slapd/back-bdb filterindex.c
by Howard Chu 09 Jul '07

09 Jul '07

quanah(a)OpenLDAP.org wrote: > Update of /repo/OpenLDAP/pkg/ldap/servers/slapd/back-bdb > > Modified Files: > filterindex.c 1.68 -> 1.69 > > Log Message: > ITS#5037 > Move db == NULL check to correct spot As we already discussed in IM, just re-ordering the tests is not sufficient. The actual test for db == NULL is wrong, you have to test the rc for the specific value (LDAP_INAPPROPRIATE_MATCHING). There are two problems - if bdb_index_param fails for any reason at all, it will not set the db, so you need to distinguish the serious failures from the benign ones. Also, if you examine the code for bdb_index_param, you'll see that it never touches the db parameter on failure, so it will remain uninitialized. -- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#4991) pcache and rwm don't play well together
by Ralf Haferkamp 09 Jul '07

09 Jul '07

Hello, slightly related to the above ITS, I have found another issue. I am not sure though if this is a bug or if the behaviour is intended. I have a setup here were the pcache and rwm-overlay is used on top of back-ldap. rwm is used to rewrite some Attributetypes unknown to the Schema of the local server to Attributetypes that are defined in the local server. As the attribute values from unknown attribute types cannot be normalized by the proxy, I am wondering if rwm should normalize them during the Mapping process? Otherwise the Values will endup un-normalized in the cache database, and I get incomplete results when requests are answered from the cache. I have a patch ready for this but I was wondering if the normalization step is left out by intention and wanted to ask before commiting my patch. -- Ralf

3 7

[Fwd: Re: imporvement to slapo-constraint (ITS#4987)]
by Gavin Henry 07 Jul '07

07 Jul '07

It would help if you sent it to openldap-devel! ;-) ---------------------------- Original Message ---------------------------- Subject: Re: imporvement to slapo-constraint (ITS#4987) From: "Emmanuel Dreyfus" <manu(a)netbsd.org> Date: Sat, July 7, 2007 8:15 pm To: "Gavin Henry" <ghenry(a)suretecsystems.com> Cc: openldap-its(a)openldap.org -------------------------------------------------------------------------- Gavin Henry <ghenry(a)suretecsystems.com> wrote: > It would be best to move this dicussion to openldap-devel(a)openldap.org now. Let's go... Summarry: I've added a new feature to slapo-constraint for constraining a value attribute the the existing values of another attribute. The idea is that you can have a catalog of allowed values (eg: for titles: Mr, Mrs, Miss) and constraint an attribute to these values Before working further on this patch (style, dod), I'd like some feeback on: 1) the way it's implemented: is there rought bugs, or is the logic fine? 2) configuration syntax: do we keep this one or do we swtich to something else? Could someone comment on the patch? -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu(a)netbsd.org

1 0

Google Build Farm Proposal news?
by Gavin Henry 06 Jul '07

06 Jul '07

Hi, Did you get anywhere with your plan Howard for the Google proposal? Gavin. -- Kind Regards, Gavin Henry. Managing Director. T +44 (0) 1224 279484 M +44 (0) 7930 323266 F +44 (0) 1224 824887 E ghenry(a)suretecsystems.com Open Source. Open Solutions(tm). http://www.suretecsystems.com/

1 0

slapd memory alloc/free functions
by Hallvard B Furuseth 06 Jul '07

06 Jul '07

#define LDAP_MEMORY_DEBUG and SLAP_NO_SL_MALLOC breaks slapd in a number of places. Some of the fixes are straightforward, but others require more sweeping changes - or leaving LDAP_MEMORY_DEBUG useless, which it has been for some time anyway. However the LDAP_MEMORY_DEBUG troubles match a Windows bug: According to ITS#4901, Windows gets heap corruption unless mallocs done in one DLL are balanced by frees done from the same DLL. (I'll summarize memory management at the end, so the uninitiated can have some clue what I'm talking about.) The main problem is memory allocated with malloc(), either in slapd or a library - in particular librewrite. proto-slap.h does #define free ch_free unless CH_FREE is #defined. ch_free(malloc(x)) ends up calling ber_memfree, and LDAP_MEMORY_DEBUG breaks ber_memfree(malloc(x)). With Windows, the freeing DLL will be liblber instead of librewrite or whatever. The simplest fix looks like a global search-and-replace with malloc & co -> ber_memalloc & co except leaving free (-> ch_free) alone in slapd. (Or use LDAP_MALLOC, LBER_MALLOC and SLAP_MALLOC and friends instead. They all expand to ber_memalloc & co.) Is there a reason why we use both malloc() and ber_memalloc()? Functionality aside, it also makes the code harder to read (and to search for bugs). I think it should be done in librewrite at least, since it is used to insert data into ber_memalloced data structures in slapd's. I suppose such a change could break some Windows module which by somehow explicitly uses _current_ free vs ber_memfree vs ber_memfree_x correctly - in particular if it uses librewrite as a library outside of slapd. Should we worry? Maybe librewrite should have its own memory handler functions which can be overridden like liblber's. Regarding the '#define free ch_free' in slapd, I'm not convinced that is a good idea. I'm sure it has saved some code which wrote free where it should have written ch_free, but it also makes it even harder to see what is going on - and apparently it can break slapd modules that use malloc() - free() on Windows. Maybe we should begin to phase it out. (First stage: /free/ch_free/ in slapd, #define CH_FREE in all slapd .c files, and make the #define free ch_free in slap.h cause some warning. Then wait indefinitely for modules to follow suit.) Summary of OpenLDAP memory management, as I understand it -- Some memory is allocated with plain malloc, but most via ber_mem*() functions in liblber. Of those, the ones ending with "_x" take an extra "context" argument. If you pass a non-NULL context and you have set malloc handler functions in liblber, ber_*_x() call these with the context. Otherwise they call plain malloc() co. slapd also has thread-local malloc heaps, used by slap_sl_malloc() & co. A thread can have a context, which has a reference to the thread's heap. Threads must not free/alloc in other threads' heaps. This avoids locks or mutexes which malloc() needs to ensure that two concurrent malloc()s do not corrupt malloc()'s heap. Slapd can use them for memory which gets allocated and freed while handling a single request (which gets handled by a single thread), I think. slapd sets slap_sl_free() co or wrappers around them as memory handlers, and a special ch_free() for the free() handler. Since it can be a bit hard to keep track of which memory comes from where, ch_free() fetches the current thread's context if passed a NULL context. Then it calls slap_sl_free if there is a context, ber_memfree otherwise. slap_sl_free in turn checks if the memory to be freed came from the context's heap, otherwise it passes it on to ber_memfree() without a context. With the '#define free ch_free', a free/ch_free/slap_sl_free/ber_memfree_x() ends up in the right place. Except if you try to free another thread's memory, or use ber_memfree[_x]() without a context to free a thread's memory, or try to free something from a plain malloc() on Windows. Oh, and finally there are wrapper functions and macros. LBER_MALLOC, LDAP_MALLOC, SLAP_MALLOC and friends, which expand to ber_memalloc & co. ch_malloc() and friends in slapd, which check that the malloc was successful and exit otherwise. (Naughty, we really ought to phase out that someday.) -- Regards, Hallvard

1 1

Alphabetised defines.sh?
by Gavin Henry 06 Jul '07

06 Jul '07

Dear all, I've been trying to follow defines.sh to find a few variables. Is there any reason the individual sections aren't alphabetised? Just wondering ;-) -- Kind Regards, Gavin Henry. Managing Director. T +44 (0) 1224 279484 M +44 (0) 7930 323266 F +44 (0) 1224 824887 E ghenry(a)suretecsystems.com Open Source. Open Solutions(tm). http://www.suretecsystems.com/

3 4

loglevel index intention?
by Quanah Gibson-Mount 02 Jul '07

02 Jul '07

I noticed that loglevel index is unused by anything currently, and I was wondering what the intention was initially behind that loglevel. There are a number of back-bdb/hdb error messages that get generated around indices that currently come out at the "any" level. I thought perhaps index might be better for them, but wasn't sure of the intent. --Quanah

2 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-devel