[EMAIL PROTECTED] writes:
> I'm aware of the NIS order number but don't have an idea of how this can
> be done for LDAP maps. I want the handling to remain as consistent as
> possible between map types. This will be an advantage when I add
> ghosting of nis+ maps.
With servers that use the modifyTimestamp and createTimestamp
operational attributes (these SHOULD be set when an object is added or
changed, according to RFC 2252), these could be used to detect if any
entry has been changed or added since last time you checked. However,
this would fail to detect any removed entries.
What you really want is probably something like lcup ("LDAP Client
Update Protocol",
<URL:http://www.ietf.org/internet-drafts/draft-ietf-ldup-lcup-06.txt>)
or ldapsync ("The LDAP Content Synchronization Operation",
<URL:http://www.ietf.org/internet-drafts/draft-zeilenga-ldup-sync-05.txt>),
which both address this problem. It appears that recent versions of
OpenLDAP support ldapsync, but neither solution is even close to
de-facto standard status.
For some years to come, any useful and portable implementation would
need to support the case where there are no timestamps and no cool
synchronization operations to help you, I'm afraid.
Thorild Sel�n
Datorf�reningen Update / Update Computer Club, Uppsala, SE
_______________________________________________
autofs mailing list
[EMAIL PROTECTED]
http://linux.kernel.org/mailman/listinfo/autofs
