openldap-software

openldap-software@openldap.org

2719 discussions

synrepl and contextCSN missing
by Raphaël 'SurcouF' Bordet 12 Jun '07

12 Jun '07

Hi, If even a master doesn't provide a contextCSN on root entry, whats happens ? Does syncrepl is always working fine ? I've some databases populated by using syncrepl and masters doesn't provides contextCSN. I'm using refreshOnly type of syncrepl and I'm getting changes only when I've just restart slapd. Any hint ? Regards, PS: I'm using OpenLDAP 2.3.35 under Solaris 10 -- Raphaël 'SurcouF' Bordet

1 0

bdb or hdb ?
by Kari Mattsson 12 Jun '07

12 Jun '07

I'm wondering... All documentation I've seen mention hdb as sibling of bdb with the only significant difference of being able to rename (sub)trees, and thus move them around. Then there is one config difference: idlcachesize shoud be 4 x cachesize when using hdb. For bdb it can be way smaller than cachesize. If the difference really is this small, 1) where is the real point in having two almost same back-ends? 2) why wouldn't everybody use hdb in the first place? --Kari Mattsson

2 1

Regarding backend database in openldap !!
by sameer 12 Jun '07

12 Jun '07

Hi, I would like to know using DB2 as the backend instead of BDB in openldap will have performance advantages. Has anyone tried integrating openldap with DB2 ? Any help would be appreciated. Rgs Sameer This e-mail and attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient's) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!

2 1

Does chain overlay support sasl binding?
by Simon Gao 12 Jun '07

12 Jun '07

Hi, I'd like to know if chain overlay currently supports sasl binding or not with OpenLDAP 2.3.35. Since both idassert-bind and chain-idassert-bind are handled by ldap backend, can I assume sasl binding should be available to chain overlay also? Appreciate your help. Thanks, Simon

2 7

Re: Problem with Schema in Openldap 2.3.19
by Eugenia Candida Oliveira de Moura 11 Jun '07

11 Jun '07

The debug in Openldap 2.3.19: >>> dnPrettyNormal: <cn=schema,cn=config> => ldap_bv2dn(cn=schema,cn=config,0) <= ldap_bv2dn(cn=schema,cn=config)=0 => ldap_dn2bv(272) <= ldap_dn2bv(cn=schema,cn=config)=0 => ldap_dn2bv(272) <= ldap_dn2bv(cn=schema,cn=config)=0 <<< dnPrettyNormal: <cn=schema,cn=config>, <cn=schema,cn=config> modifications: add: olcAttributeTypes one value, length 141 conn=0 op=1 MOD dn="cn=schema,cn=config" conn=0 op=1 MOD attr=olcAttributeTypes oc_check_required entry (cn=schema,cn=config), objectClass "olcSchemaConfig" oc_check_allowed type "objectClass" oc_check_allowed type "cn" oc_check_allowed type "olcObjectIdentifier" oc_check_allowed type "olcAttributeTypes" oc_check_allowed type "olcObjectClasses" oc_check_allowed type "structuralObjectClass" oc_check_allowed type "entryUUID" oc_check_allowed type "creatorsName" oc_check_allowed type "createTimestamp" oc_check_allowed type "entryCSN" oc_check_allowed type "modifiersName" oc_check_allowed type "modifyTimestamp" slapd: line 0: Unexpected token before SYNTAX 1.3.6.1.4.1.1466.115.121.1.15SIN GLE-VALUE ) AttributeTypeDescription = "(" whsp numericoid whsp ; AttributeType identifier [ "NAME" qdescrs ] ; name used in AttributeType [ "DESC" qdstring ] ; description [ "OBSOLETE" whsp ] [ "SUP" woid ] ; derived from this other ; AttributeType [ "EQUALITY" woid ] ; Matching Rule name [ "ORDERING" woid ] ; Matching Rule name [ "SUBSTR" woid ] ; Matching Rule name [ "SYNTAX" whsp noidlen whsp ] ; see section 4.3 [ "SINGLE-VALUE" whsp ] ; default multi-valued [ "COLLECTIVE" whsp ] ; default not collective [ "NO-USER-MODIFICATION" whsp ]; default user modifiable [ "USAGE" whsp AttributeUsage ]; default userApplications ; userApplications ; directoryOperation ; distributedOperation ; dSAOperation whsp ")" olcAttributeTypes: value #-1: <olcAttributeTypes> handler exited with 1! send_ldap_result: conn=0 op=1 p=3 send_ldap_result: err=80 matched="" text="<olcAttributeTypes> handler exited wit h 1" send_ldap_response: msgid=2 tag=103 err=80 ber_flush: 55 bytes to sd 12 <olcAttributeTypes > handler exited with 1 ldap_write: want=55, written=55 0000: 30 35 02 01 02 67 30 0a 01 50 04 00 04 29 3c 6f 05...g0..P...)<o 0010: 6c 63 41 74 74 72 69 62 75 74 65 54 79 70 65 73 lcAttributeTypes 0020: 3e 20 68 61 6e 64 6c 65 72 20 65 78 69 74 65 64 > handler exited 0030: 20 77 69 74 68 20 31 with 1 conn=0 op=1 RESULT tag=103 err=80 text=<olcAttributeTypes> handler exited with 1 daemon: activity on 1 descriptor daemon: activity on: 12r daemon: read active on 12 connection_get(12) connection_get(12): got connid=0 When the new attribute is add, is being added a value "1" in the end of the olcAttributeType, for example, olcAttributeType1. But I do not know because. 2007/6/11, Quanah Gibson-Mount <quanah(a)zimbra.com>: > > --On Monday, June 11, 2007 6:35 AM +0200 Dieter Kluenter > <dieter(a)dkluenter.de> wrote: > > > "Eugenia Candida Oliveira de Moura" < eugeniacandida(a)gmail.com> writes: > > > >> Hi, > >> > >> I'm using openldap 2.3.19 and when I try to add to a new attribute in > >> the entry cn= schema,cn=config I have the following error: > >> <olcAttributeTypes> handler exited with 1 > >> > >> Why this error occurs? > >> Some ideia? > > > > Could you please be a bit more verbose on the error? Something like > > debugging -d-1 would probabely be of help. > > And get the debug info from a recent version of OpenLDAP. 2.3.19 is quite > old. > > --Quanah > > > -- > Quanah Gibson-Mount > Principal Software Engineer > Zimbra, Inc > -------------------- > Zimbra :: the leader in open source messaging and collaboration >

2 1

move subtree !!
by sameer 11 Jun '07

11 Jun '07

Hi, Does openldap support move subtree operation. ? I have a requirement where i need to move one subtree to other location. Can i achieve this without deleting and adding again. Rgs Sameer This e-mail and attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient's) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!

2 1

indexes and multiple values
by David Schmitter 11 Jun '07

11 Jun '07

hi all it seems that recent openldap versions don't allow eq indexes if there are multiple values (per object) for an attribute. if i use an eq index on such an attribute queries will not match for any of the multiple values. this was possible with openldap 2.0 using the ldbm backend. any ideas? cheers david

2 1

Problem with Schema in Openldap 2.3.19
by Eugenia Candida Oliveira de Moura 11 Jun '07

11 Jun '07

Hi, I'm using openldap 2.3.19 and when I try to add to a new attribute in the entry cn=schema,cn=config I have the following error: <olcAttributeTypes> handler exited with 1 Why this error occurs? Some ideia? Thanks.

4 3

ldap manual "other stuff"
by Piotr Wadas 11 Jun '07

11 Jun '07

Hello, from ldap_init(3) "ldap_open() opens a connection to an LDAP server and allocates an LDAP structure [...] typedef struct ldap { /* ... other stuff you should not mess with ... */ char ld_lberoptions; int ld_deref; [...]" Ehmm, what is "other stuff I shouldn't mess with" ? :) Regards, Piotr

2 1

ber_scanf and ber_printf strangeness
by Szombathelyi György 10 Jun '07

10 Jun '07

Hi! I'm developing kldap, a Qt wrapper for LDAP-functions. When I tested ber_scanf and ber_printf functions, I found this strangeness: Encode a sequence of octet strings via ber_printf ber_printf(ber,"{v}",list_of_strings); But decoding only succeeds if I use the following scanf formats: ber_scanf(ber,"v",...) - yes, without '{}', or ber_scanf(ber,"{ooo}") As I read the ber_scanf man page, 'v' format actually decodes a sequence of octet strings, so my examples are correct according to these. But the code example on the end shows that '{v}' should be used. So what is the right way? Regards, György

2 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-software