Rafal Kaminski wrote:
Hi,
Please help me or tell - if this is possible to make this one?
It is not possible :-(
Search the archive.
Short answer:
ldapcompare will find the dyngroup members; ldapsearch will not
I fight with this 2 days and I can't found resolve.
Thanks!
BR,
Rafal
On 05/01/11 14:33 +0100, Jaap Winius wrote:
Hi folks,
Compiling the Debian sources for the OpenLDAP packages can take over
an hour on my relatively fast workstation. Much of that time seems to
be spent running a slapd server with all kinds of test routines. Is
that what's actually going on?
I have written up documentation on performance tuning OpenLDAP 2.4 that
covers most other areas, for my work @ Zimbra, you can find it at:
http://wiki.zimbra.com/wiki/OpenLDAP_Performance_Tuning_6.0
It's based on you using Zimbra's tools to automatically update the
configuration database,
Hello Howard,
By default an index slot can only maintain 65535 records before it overflows
and loses precision. Once it loses precision, you tend to get results like
this. If you need to accomodate larger indices you can tweak a constant in
back-bdb/back-bdb.h and recompile. You'll probably
Steeg Carson wrote:
Hello Howard,
By default an index slot can only maintain 65535 records before it overflows
and loses precision. Once it loses precision, you tend to get results like
this. If you need to accomodate larger indices you can tweak a constant in
back-bdb/back-bdb.h and
I'm running openldap-2.3.43-12.el5 on a RHEL 5.5 system:
I find that TLS will not work if I use uri ldap://10.3.5.207/ in
/etc/ldap.conf on my clients.
TLS magically starts working if I use the deprecated host directive instead:
So if I use host 10.3.5.207 instead everything starts working:
On 1/6/2011 19:18, Michael Starling wrote:
I'm running openldap-2.3.43-12.el5 on a RHEL 5.5 system:
I find that TLS will not work if I use *uri ldap://10.3.5.207/ *in
/etc/ldap.conf on my clients.
TLS magically starts working if I use the deprecated host directive
instead:
So if I use
