Ian Kent writes:
> But, at this stage, autofs isn't going to be listening it's going to be
> asking?
LCUP provides a syncOnly mode if you don't want to listen persistently
but instead occasionally ask for changes. If I've understood it
correctly, it would work basically like this:
1. The automounter downloads a table from the LDAP server, attaching
a Sync Request control (with no synchronisation cookie) to the
search request.
2. The LDAP server returns the table, together with a synchronisation
cookie.
3. Later, the automounter may ask the server: "What changes have been
made to this table since you handed out this synchronisation
cookie?" (Yes, I know, there is no such thing as a table from the
LDAP server's point of view, but you get the point.) The server
will then tell the client about any changes since then, including
added/deleted entries, and return a new synchronisation cookie to
be used in the next sync request. Repeat each time we want to
check for modifications.
NOTE: I believe the server is not required to keep this
synchronisation state around. The server may refuse, in which case
we go back to 1. and download the table from scratch.
The advantage with this would be that the automounter can keep its
tables perfectly up to date without having to retrieve the tables in
their entirety over and over again.
(Alternatively, LCUP has a persistent mode where you constantly listen
for changes instead of requesting them when required. That would
probably not scale as well as using the syncOnly mode.)
Thorild Selén
Datorföreningen Update / Update Computer Club, Uppsala, SE
_______________________________________________
autofs mailing list
[email protected]
http://linux.kernel.org/mailman/listinfo/autofs
