it was about replication
CSN The Change Sequence Number (CSN) used OpenLDAP to identify
changes in a replicated configuration. CSNs appear to be only defined
in an expired RFC draft draft-chu-ldap-csn-xx.txt and for version 2.4
in this FAQ to consist of a timestamp - including microseconds, an
operation-within-second counter (6 octets), a 3 octet replica id (as
defined by ServerID) and a 6 octet counte-within-modify operation.
Yes it is still alive who knows what happens in the future ;)
On Wed, Mar 30, 2011 at 12:04 PM, Emmanuel Lecharny <elecharny(a)gmail.com> wrote:
On 3/30/11 10:51 AM, Omer Faruk SEN wrote:
> I have a dump of Sun LDAP Directory server (6.3.1) I see
> dn: cn=me,ou=groups,dc=me,dc=com
> nsUniqueId: 1255060a-46e511dd-803ce5f5-385faa0b
> objectClass;vucsn-4869456e0009002d0000: top
> objectClass;vucsn-4869456e0009002d0000: groupOfUniqueNames
> cn;vucsn-4869456e0009002d0000;mdcsn-4869456e0009002d0000: everyone
> description;vucsn-4869456e0009002d0000: everyone
> lines what is the meaning of vucsn,mdcsn and adcsn?
What about asking on the Sun DS mailing list (if it's still alive :) ?