I'm writing a script that acts on changes in LDAP.
I've abandoned this idea. The ldapsearch utility doesn't decode SyncInfo messages which provide valuable information. Instead, it simply prints "SyncInfo Received". This is worse than printing nothing at all because it causes my LDIF parser to choke.
I think either the slapd-perl or slapd-shell backends are better suited to my needs than tailing the output of ldapsearch -Esync/rp
Thomas
--On Monday, March 23, 2015 9:45 AM -0400 Thomas Cort linuxgeek@gmail.com wrote:
I'm writing a script that acts on changes in LDAP.
I've abandoned this idea. The ldapsearch utility doesn't decode SyncInfo messages which provide valuable information. Instead, it simply prints "SyncInfo Received". This is worse than printing nothing at all because it causes my LDIF parser to choke.
I think either the slapd-perl or slapd-shell backends are better suited to my needs than tailing the output of ldapsearch -Esync/rp
I think there are a number of potential options you could use...
python-ldap (python) perl-ldap (perl) UnboundID SDK (Java) org.apache.directory.api (Java)
etc.
--Quanah
--
Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration
Thomas Cort wrote:
I'm writing a script that acts on changes in LDAP.
I've abandoned this idea. The ldapsearch utility doesn't decode SyncInfo messages which provide valuable information. Instead, it simply prints "SyncInfo Received". This is worse than printing nothing at all because it causes my LDIF parser to choke.
I think either the slapd-perl or slapd-shell backends are better suited to my needs than tailing the output of ldapsearch -Esync/rp
I'd rather recommend not to use slapd-perl or slapd-shell backends.
I'd recommend to look into these options: 1. back-sock (also usable as overlay) 2. changes written to a separate DB slapo-accesslog 3. implement your own syncrepl client with a decent scripting language. For Python see [1], not sure whether there is a decent syncrepl module for Perl.
All options have pros and cons.
Ciao, Michael.
Am Mon, 23 Mar 2015 20:55:51 +0100 schrieb Michael Ströder michael@stroeder.com:
Thomas Cort wrote:
I'm writing a script that acts on changes in LDAP.
I've abandoned this idea. The ldapsearch utility doesn't decode SyncInfo messages which provide valuable information. Instead, it simply prints "SyncInfo Received". This is worse than printing nothing at all because it causes my LDIF parser to choke.
I think either the slapd-perl or slapd-shell backends are better suited to my needs than tailing the output of ldapsearch -Esync/rp
I'd rather recommend not to use slapd-perl or slapd-shell backends.
I'd recommend to look into these options:
- back-sock (also usable as overlay)
- changes written to a separate DB slapo-accesslog
- implement your own syncrepl client with a decent scripting
language. For Python see [1], not sure whether there is a decent syncrepl module for Perl.
Net::LDAP::Control::SyncDone Net::LDAP::Control::SyncRequest Net::LDAP::Control::SyncState
-Dieter
openldap-technical@openldap.org
-
Dieter Klünter -
Michael Ströder -
Quanah Gibson-Mount -
Thomas Cort