Messages in this thread | | | Date | Fri, 30 Apr 1999 12:19:47 +0200 | From | Thomas Pornin <> | Subject | NFS and cached atime |
| |
In article <7gae80$2jd$1@q.cistron.nl> you write: > Right now my "you have new mail" doesn't work, because even if I read > my mail, the atime stamp doesn't get updated.
For the last year, I used a Linux box (Alpha) with many 2.1.x and 2.2.x kernels, with mailbox on a NFSv2 server (SunOS 4.1.x) and the "new mail" message would never fail (except with early versions of the NFSv3 patch, which is now correct).
I use my own "new mail" detection and it reports new mail if and only if mtime is strictly greater than atime. And this works both on NFSv2 and NFSv3. You do not want to update the atime each time you read from a file (it would defeat the purpose of read-caching) and therefore its value is not reliable alone. However, upon modification, atime is correctly updated.
What is your NFS server ? The problem might be there. Here, SunOS and Solaris servers.
--Thomas Pornin
- 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/
| |