On Thu, Jan 15, 2009 at 12:17 AM, Ian Kent <ra...@themaw.net> wrote: > Sorry, I meant the logic that reloads the file map if it's been > > modified. I know that autofs v4 checked the mtime, but I can't see > > where autofs v5 does that. > > Yeah, I didn't think I got rid of that. > > But the check for a mismatch between the cache and a file key lookup > should be sufficient to only cause a read when the map has actually > changed. I guess we could get multiple HUP signals, one following just > after the other has finished, but that would be a system admin error and > you'd probably want to know about that since we can't make a similar > check some other map sources. I probably should get around to removing > the mtime stuff all-together, perhaps you could let me know if things > work as they should (or not) so I can clean (or fix) that up.
Are you saying that every lookup for an indirect map will hit the file? If that's the case, then what's the point of the cache? If that's not the case, but you're not checking the mtime either, then how do you know when the file has been modified? (Please excuse the silly questions.)
_______________________________________________ autofs mailing list autofs@linux.kernel.org http://linux.kernel.org/mailman/listinfo/autofs
