On Thu, 20 Nov 2003, H. Peter Anvin wrote:Runtime configureable? I think somebody can be interested in 'timeinterval updates',
Ian Kent wrote:
That's correct.To fit in with the existing framework I would need to require the entire map returned for a NULL key.
A better option is probably to update periodically. You still need toAnd of course autofs needs to deal with the consequences of the map
changing underneath it.
I normally reread the map and try again on lookup failure. There is the HUP signal to do a manual map reread.
be able to handle query of a mount point that you don't know about
(might have appeared anew) or a mount point you thought exist not being
found.
The above works that way without the update.
I'm not sure that a periodic update really gets us much. Since in most sites maps change infrequently.
some in 'just before request' or 'never'(could be done in map itself).
If I return to my task then I have two solutions:
On the other hand at work we run a cron every night on all our machines to trigger an update of the maps.
1) User space daemon that cache all needed info about workgroup. So it wouldn't be
much overhead to touch programm map on every request.
2) Programm map do all things only when it's called without arguments. Sometimes
network can take much time to finish and I have to use periodicaly update calls(~30min).
So I vote for runtime configuration of interval: value > 0 - time period in seconds(msec,min or other) value = 0 - every time value < 0 - never
I think it's normal to configure it due userspace daemon startup.
Best regards. Ruslan.
So I'm on the fence here?
_______________________________________________ autofs mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/autofs