Date: Fri, 19 Dec 2014 15:12:01 -0500 (EST) From: Garrett Wollman <wollman@hergotha.csail.mit.edu> To: jilles@stack.nl Cc: freebsd-arch@freebsd.org Subject: Re: Change default VFS timestamp precision? Message-ID: <201412192012.sBJKC1rW086109@hergotha.csail.mit.edu> References: <201412161348.41219.jhb@freebsd.org> <77322.1418933100@critter.freebsd.dk> <77371.1418933642@critter.freebsd.dk> <7567696.mqJ3jgzJgL@ralph.baldwin.cx> <82135.1419010861@critter.freebsd.dk> <20141219194800.GA29107@stack.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <20141219194800.GA29107@stack.nl>, jilles@stack.nl writes: >Because there is no API to set timestamps with nanosecond resolution, >and therefore a cp -p copy of a file will appear older than the original >with 99.9% probability. I think that is undesirable. But that's something we can easily fix -- and should have done, years ago. Why don't we just *do* that? Of course, in the case of NFS clients, where this issue is most severe, the RPCs are already defined. The underlying VOP_SETATTR has no trouble with nanoseconds, either. It's just a matter of providing a standard library interface (and associated system call(s)) to do it, and since Linux has already implemented this, we can just implement that interface and applications will get it "for free". -GAWollman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201412192012.sBJKC1rW086109>