Hi all,
This is not a problem, just a question to understand the things
behind the scenes.
I am just playing around with some LDAP frontends helping the user
to add the correct attributes depending on the selected objectclass(es)
when creating new LDAP entries.
A have tried to add an entry
--On Wednesday, January 27, 2010 12:58 PM +0100 Stefan Palme
pa...@kapott.org wrote:
Hi all,
This is not a problem, just a question to understand the things
behind the scenes.
I am just playing around with some LDAP frontends helping the user
to add the correct attributes depending on the
Hi,
I need to set up a LDAP production server with 800.000 entries.
Performance and stability are
my main concern, I expect around 250 binds and 50 ldapupdate/insert per
minute.
The machine is a SunFire6900 with 8 sparc US-IV+ CPUs and I'd like to
dedicate around 500MB
of ram to OpenLdap (more,
--On Wednesday, January 27, 2010 7:06 PM +0100 Stefano Zanmarchi
zanmar...@gmail.com wrote:
Hi,
I need to set up a LDAP production server with 800.000 entries.
Performance and stability are
my main concern, I expect around 250 binds and 50 ldapupdate/insert per
minute.
The machine is a
We found out that this call :
ldap_msgfree(res);
does not get executed because the LDAPMessage is NULL (res is null) in case the
timeout is on the client side.
There is any other way to clean it?
OpenLDAP 2.4.20 does not have this problem. I compared the
olcDatabase={0}config.ldif and olcDatabase={1}hdb.ldif files between 2.4.20
and 2.4.21 and noticed that the olcSyncrepl attribute value from 2.4.21
contains a uri= whereas the olcSyncrepl attribute from 2.4.20 (working
version) does not.
So I copied slapd.d from 2.4.20 to 2.4.21 and that seems to get 2.4.21 slapd
going. Is this going to cause me issues down the road? Can 2.4.21 use
cn=config entries from 2.4.20? My single provider / multiple consumers
syncrepl setup appears to be working as expected in 2.4.21.
Thanks,
Hung
On
