Thanks!
For now I wrote a script that compares the contextCSN of the root object,
but I am definitely going to play around with that backend when I get the
chance.
All the best,
Eli
2011/11/14 Michael Ströder mich...@stroeder.com
Howard Chu wrote:
Michael Ströder wrote:
E.S. Rosenberg
2011/11/14 Michael Ströder mich...@stroeder.com
Howard Chu wrote:
Michael Ströder wrote:
E.S. Rosenberg wrote:
I was wondering is it possible to set a slapd syncprov consumer to
trigger a script when it receives changes to the db (updates of
specific attributes).
You might want to
Eli,
E.S. Rosenberg schrieb (13.11.2011 17:13 Uhr):
I was wondering is it possible to set a slapd syncprov consumer to
trigger a script when it receives changes to the db (updates of
specific attributes).
I think you might be able to replicate to a server instance with
back-perl or back-shell
E.S. Rosenberg wrote:
I was wondering is it possible to set a slapd syncprov consumer to
trigger a script when it receives changes to the db (updates of
specific attributes).
You might want to try something with a synclrepl consumer served by back-sock.
But I think getting this right is almost
Michael Ströder wrote:
E.S. Rosenberg wrote:
I was wondering is it possible to set a slapd syncprov consumer to
trigger a script when it receives changes to the db (updates of
specific attributes).
You might want to try something with a synclrepl consumer served by back-sock.
But I think
Howard Chu wrote:
Michael Ströder wrote:
E.S. Rosenberg wrote:
I was wondering is it possible to set a slapd syncprov consumer to
trigger a script when it receives changes to the db (updates of
specific attributes).
You might want to try something with a synclrepl consumer served by
I was wondering is it possible to set a slapd syncprov consumer to
trigger a script when it receives changes to the db (updates of
specific attributes).
Basically we have a bunch of flat files that are created and
maintained based on information kept in slapd which need to either:
- run every X
