[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Monitoring 2.3.43?

To: <openldap-technical@openldap.org>
Subject: Re: Monitoring 2.3.43?
From: Turbo Fredriksson <turbo@bayour.com>
Date: Sat, 16 Jun 2012 19:02:10 +0200
In-reply-to: <ad60b7960823698cd79c8a34689954e0@bayour.com>
References: <e5e0f35a1ddc9080f1c03578aef57c0f@bayour.com> <4FBE02E4.1080505@eurobjects.com> <20120525114649.GB24056@slab.skills-1st.co.uk> <65692d1a4eb4f994f945f9ff9310c306@bayour.com> <4FDC9B0F.9090109@symas.com> <ad60b7960823698cd79c8a34689954e0@bayour.com>
User-agent: Binero Webmail/0.5.1

On Sat, 16 Jun 2012 17:49:07 +0200, Turbo Fredriksson wrote:

After monitoring a colleagues batch modifications, I now see that the
contextCSN now match:

    paragon:    20120616153755.474331
    kelvin:     20120616153755.474331

This, BESPITE that the actual ppolicy does NOT exist on kelvin!


And even worse: Some modifications does not propagate to the slaves!
Sometimes. Running his script again, the changes seems to be there..
--

... but you know as soon as Oracle starts waving its wallet at aCompany it's time to run - fast.

/illumos mailing list

Follow-Ups:
- Re: Monitoring 2.3.43?
  - From: Chris Jacobs <Chris.Jacobs@apollogrp.edu>

References:
- Re: Monitoring 2.3.43?
  - From: Turbo Fredriksson <turbo@bayour.com>
- Re: Monitoring 2.3.43?
  - From: Howard Chu <hyc@symas.com>
- Re: Monitoring 2.3.43?
  - From: Turbo Fredriksson <turbo@bayour.com>

Prev by Date: Re: Monitoring 2.3.43?
Next by Date: Re: Monitoring 2.3.43?
Index(es):
- Chronological
- Thread