Re: Monitoring 2.3.43?

On Sat, 16 Jun 2012 07:41:19 -0700, Howard Chu wrote:

Turbo Fredriksson wrote:

...

  paragon:      20120616082046.474977
  kelvin:       20120616081559.003550

The overlay must be configured on every server for the operational attributes to be replicated.

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!

Isn't this somewhat of a problem? If these values matches, but the DB doesn't, can contextCSN actually be used for this (monitoring syncing)? -- ... but you know as soon as Oracle starts waving its wallet at a Company it's time to run - fast. /illumos mailing list