Is there a standard way to recover a local entry when its proxied entry is moved, that is, when a remote DN changes? It looks like the local entry and its attribute values become inaccessible via ldapsearch. I found the orphaned entry in the output of slapcat, but the man page warning about stopping slapd before running slapcat makes that seem like an impractical way to find and recover the orphans.
Thank you.
Steve Eckmann wrote:
Is there a standard way to recover a local entry when its proxied entry is moved, that is, when a remote DN changes? It looks like the local entry and its attribute values become inaccessible via ldapsearch. I found the orphaned entry in the output of slapcat, but the man page warning about stopping slapd before running slapcat makes that seem like an impractical way to find and recover the orphans.
None of the current backends require slapd to be stopped before running slapcat.
Thanks, Howard. That was going to be my next question.
Regards, Steve
-----Original Message----- From: Howard Chu [mailto:hyc@symas.com] Sent: Friday, June 14, 2013 11:14 AM To: Steve Eckmann; openldap-technical@openldap.org Subject: Re: translucent overlay and "orphaned" local entry when remote entry moves
Steve Eckmann wrote:
Is there a standard way to recover a local entry when its proxied entry is moved, that is, when a remote DN changes? It looks like the local entry and its attribute values become inaccessible via ldapsearch. I found the orphaned entry in the output of slapcat, but the man page warning about stopping slapd before running slapcat makes that seem like an impractical way to find and recover the orphans.
None of the current backends require slapd to be stopped before running slapcat.
openldap-technical@openldap.org
-
Howard Chu -
Steve Eckmann