https://bugs.openldap.org/show_bug.cgi?id=10424
--- Comment #5 from Ondřej Kuzník <[email protected]> --- On Wed, Feb 11, 2026 at 03:42:42PM +0000, [email protected] wrote: > Actually since we already have a sync_use_subentry option, this wouldn't be > too > difficult to support. It just would create the subentry under the consumer's > searchbase instead of under the context entry. It's not "just" the subentry, sure, that bit is "easy", it's that the rest of syncrepl expects there to be one context for each DB, this would need to be split up per "sub-suffix" as well and then there's the interaction with accesslog and especially syncprov (just *what* is the right information to even forward?). It might not be "hard to do" but the question I can't answer yet is "is it hard to do *right*?" That's without considering whether our testing infrastructure is capable of covering a reasonable chunk of what we need to test. -- You are receiving this mail because: You are on the CC list for the issue.
