On Thu, Mar 20, 2025 at 04:04:44PM +0000, Windl, Ulrich wrote: > not I did not try that. Mostly because I think moving expresses the > actual operation more clearly in LDIF. But in the mean time I edited > the config LDIF (cutting and pasting the object, then adjusting the > DN. I wonder whether the problem might be that the new RDN is the same > as the old RDN 😉
Hi Ulrich, yes, you're not supposed to do that so the backend will refuse. cn=config doesn't allow every operation for every type of entry as entries in that database are not just that, they represent actual data and relationships of a running server and e.g. renames might not make sense in the first place. > On 3/20/2025 8:16 AM, Windl, Ulrich wrote: > Reading > https://kb.symas.com/en_US/configuration/configure-delta-syncrepl I > realized that my syncprov is on the original database, not on the > accesslog. That document (and the Admin Guide's section on deltasync) say you should configure syncprov on the replicated DB and *another* syncprov (with clearly different options) on its accesslog DB as well. Regards, -- Ondřej Kuzník Senior Software Engineer Symas Corporation http://www.symas.com Packaged, certified, and supported LDAP solutions powered by OpenLDAP
