Hi!
When trying to require integrity for LDAP connections by specifying ssf=1 in
Security, I have a problem with Perl where the cat bites its tail:
It's recommended to query the root DSE for TLS extension before trying to use
TLS like this:
my $dse = $ldap-root_dse();
if
--On Wednesday, July 24, 2013 4:08 PM +0200 Ulrich Windl
ulrich.wi...@rz.uni-regensburg.de wrote:
Hi!
When trying to require integrity for LDAP connections by specifying
ssf=1 in Security, I have a problem with Perl where the cat bites its
tail:
It's recommended to query the root DSE for TLS
On Wed, 24 Jul 2013 07:59:21 -0700 Quanah Gibson-Mount qua...@zimbra.com
wrote
--On Wednesday, July 24, 2013 4:08 PM +0200 Ulrich Windl
ulrich.wi...@rz.uni-regensburg.de wrote:
Hi!
When trying to require integrity for LDAP connections by specifying
ssf=1 in Security, I have a problem
Hello,
I use the 2.4.35 version of openldap.
I have three master ldap mulit-delta-sync: ldap01, ldap02 and ldap03.
We import data ldap03 on two others by a copy of the FileSystem.
Upon restart, the three seem OK but we have in the logs files 3GB of
message like
this:
Jul 22 20:10:46 ldap02
wondering what the best strategy to achieve atomic updates with LMDB.
what i am trying to achieve is a read then update atomic action given a highly
concurrent use case, for example, if a key/value pair represents a counter,
how does one increment or decrement the counter atomically.
i am
--On Wednesday, July 24, 2013 8:25 PM +0200 Ludovic Brochard
killerp...@gmail.com wrote:
Hello,
I use the 2.4.35 version of openldap.
I have three master ldap mulit-delta-sync: ldap01, ldap02 and ldap03.
We import data ldap03 on two others by a copy of the FileSystem.
Upon restart, the
Tomer Doron wrote:
wondering what the best strategy to achieve atomic updates with LMDB.
what i am trying to achieve is a read then update atomic action given a
highly concurrent use case, for example, if a key/value pair represents a
counter, how does one increment or decrement the counter
howard - thank you for the prompt reply and for putting this wonderful library
together.
to clarify my understanding, can you elaborate a little on the locking lmdb tx
provide cross threads and processes? in particular
1. do they provide a writer lock by default and one needs to flag
Tomer Doron wrote:
howard - thank you for the prompt reply and for putting this wonderful library
together.
to clarify my understanding, can you elaborate a little on the locking lmdb tx
provide cross threads and processes? in particular
1. do they provide a writer lock by default and one
