On Fri, 25 May 2012 12:46:50 +0100, Andrew Findlay wrote:
In normal operation it should
be enough to read the contextCSN attribute from the root of the
replicated subtree on each server:
Ok, most of the servers are now upgraded, but unfortunatly there's
two that can't (for various reasons) not
Turbo Fredriksson wrote:
On Fri, 25 May 2012 12:46:50 +0100, Andrew Findlay wrote:
In normal operation it should
be enough to read the contextCSN attribute from the root of the
replicated subtree on each server:
Ok, most of the servers are now upgraded, but unfortunatly there's
two that
On Sat, 16 Jun 2012 07:41:19 -0700, Howard Chu wrote:
The overlay must be configured on every server for the operational
attributes to be
replicated.
Ah, ok. Thanx. That's a problem then, because CentOS 5.x don't seem to
have that
compiled in...
Ah, well. We're not going to use ppolicy on
On Sat, 16 Jun 2012 10:27:55 -0700, Chris Jacobs wrote:
That makes me wonder what his script is doing... Sounds like the
script is handling some part of the replication.
Nope, nothing fancy. 15-20 lines of bash code. I helped him write it
:).
Just an ldapmodify with some error checking
On Thu, May 24, 2012 at 12:44:04PM +0300, Nick Milas wrote:
But in the meantime, is there any way to know/figure out if the
master and it's slave(s) are in
sync?
This was discussed only yesterday!
Supposing you are replicating the full DIT: slapcat both ends, use
the ldifsort utility to
First of: I know it's old, we ARE going to upgrade at the next service
interval in a few weeks!
But in the meantime, is there any way to know/figure out if the master
and it's slave(s) are in
sync?
One idea, of using a special object which is written to every x minute
and then checked for
On 24/5/2012 12:13 μμ, Turbo Fredriksson wrote:
But in the meantime, is there any way to know/figure out if the master
and it's slave(s) are in
sync?
This was discussed only yesterday!
Supposing you are replicating the full DIT: slapcat both ends, use the
ldifsort utility to sort the
