Re: 2.6.4 replication oddness

--On Friday, August 11, 2023 2:10 PM -0400 Brendan Kearney wrote: thats fair.  what info is appropriate, and at what depth?  high level, it's a 3 node cluster, with syncprov, refint, memberof, dynlist, back_meta and sssvlv modules loaded.  the cn=config database is only a olcDatabaseConfi

Re: ldap_add: Naming violation (64) additional info: value of single-valued naming attribute 'dc' conflicts with value present in entry

--On Thursday, August 17, 2023 7:25 AM +0530 Kaushal Shriyan wrote: # cat mydomain.ldif dn: dc=corporate,dc=mydomain,dc=in objectClass: dcObject objectClass: organization dc: mydomain o: mydomain # ldapadd -f mydomain.ldif -D cn=admin,dc=corporate,dc=mydomain,dc=in -W  adding new entry

ldap_add: Naming violation (64) additional info: value of single-valued naming attribute 'dc' conflicts with value present in entry

Hi, I am running the below mentioned openldap server version on CentOS Linux release 7.9.2009 (Core). The details are as follows. # cat /etc/os-release NAME="CentOS Linux" VERSION="7 (Core)" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="7" PRETTY_NAME="CentOS Linux 7 (Core)" ANSI_COLOR="0;31" CPE

slapd module thread synchronization and portability. __atomic_xxx().

Hi OpenLDAP affiliates, I'm working on a slapd module and have started looking at thread safety. I've noticed that lloadd uses __atomic_xx GCC builtins but slapd does not. Is there are reason for this? Does lloadd compile and run on all the same targets that slapd does?   Sean. -- This ema