Subject: Re: kern/28472: NFS client gets atime wrong
To: YAMAMOTO Takashi <firstname.lastname@example.org>
From: Brian Marcotte <email@example.com>
Date: 12/03/2004 14:13:26
> > Example where atime is NOT updated when it should be:
> it seems like an expected behaviour because the file data is cached locally
> and the server will get only non-READ requests like GETATTR which doesn't
> update atime. i'm not sure why it doesn't occur on 1.5.
Okay, I take this part back. While the second test does the right thing
on FFS, it is consistent on NFS in NetBSD versions 1.5, 1.6, and 2.0.
The first problem is the important one though. Many of our customers
are complaining they don't get notified of new mail.