[EMAIL PROTECTED] writes:
test007-replication 1.67 - 1.68
test018-syncreplication-persist 1.35 - 1.36
ldapmodify doesn't return an LDAP error code
How did we miss that for so long?
I based most of my tests on the assumption it did, but I experimentally
found out that sometimes
Pierangelo Masarati writes:
To: Hallvard B Furuseth [EMAIL PROTECTED]
Maybe we should change all the LDAP tools to always return some
LDAP error code, and some special code when it cannot or when an
LDAP code does not make sense?
The point is: LDAP error codes are integers, while command
Pierangelo Masarati wrote:
Maybe we should change all the LDAP tools to always return some
LDAP error code, and some special code when it cannot or when an
LDAP code does not make sense?
The point is: LDAP error codes are integers, while command return codes
for portability __should__
This code is not in its final form, please ignore for now.
[EMAIL PROTECTED] wrote:
Update of /repo/OpenLDAP/pkg/ldap/include
Modified Files:
ldap.h 1.286 - 1.287
Log Message:
ITS#4017 support Diffie-Hellman parameters for multiple key lengths
CVS Web URLs:
I recently had to process some 40,000+ modifications through my set of
directory servers. Initially, I tested my changes through my dev boxes
(2.3/HEAD using syncrepl). This run took approximately 2 hours, but the
slaves were modified essentially as the master was. This length of time
At 05:31 PM 10/5/2005, Quanah Gibson-Mount wrote:
I recently had to process some 40,000+ modifications through my set of
directory servers. Initially, I tested my changes through my dev boxes
(2.3/HEAD using syncrepl). This run took approximately 2 hours, but the
slaves were modified
Quanah Gibson-Mount wrote:
I recently had to process some 40,000+ modifications through my set
of directory servers. Initially, I tested my changes through my dev
boxes (2.3/HEAD using syncrepl). This run took approximately 2
hours, but the slaves were modified essentially as the master
