> I just noticed that even if I mount my NFS mailspool with noac, the
> atime stamp doesn't get updated when I read the file. This ofcourse
> is because the file is cached in memory, and NFS has no open/close.
> It happens on both 2.0.36 and 2.2.7
>
> Right now my "you have new mail" doesn't work, because even if I read
> my mail, the atime stamp doesn't get updated.
>
> Sounds like upon a read, the NFS client should update the atime on
> the server even if the file was cached. Ofcourse this shouldn't
> happen too often - perhaps acatimemin and acatimemax mount options
> should be considered? Or as a workaround only after the first read()
> on a freshly opened file?
This is all fairly easy to implement. I'd suggest just comparing the
cached value of atime with the current time, and updating it in
nfs_file_read if the discrepancy exceeds some timeout value.
Dunno about adding an extra mount option though: why not use the
ordinary attribute caching timeouts and keep things simple? IMHO mount
is already bloated with enough unnecessary NFS options.
What are people's feelings about this?
Cheers,
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/