Messages in this thread | | | Subject | Re: [BUG] NFS no longer updates file modification times appropriately | From | Trond Myklebust <> | Date | Mon, 07 Jun 2004 12:20:11 -0400 |
| |
På må , 07/06/2004 klokka 12:13, skreiv Joe Korty: > > > > > In which case we > > > could defer a timestamp-on-write only when it is still in the same second > > > as the previous write, but don't defer when a new second rolls around > > > on the client. That would reduce timestamp updates to at most one per > > > second per inode per client, while preserving old NFS behavior. > > > > Exactly why should we go to all this trouble? > > For compatibility?
With what? There has never been a standard other than the close-to-open.
Cheers, Trond - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |