Date: Fri, 17 Jan 2003 15:30:02 -0800 (PST) From: Bruce Evans <bde@zeta.org.au> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/47168: st_*timespec tv_nsec zero on file creation Message-ID: <200301172330.h0HNU2Sj022732@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/47168; it has been noted by GNATS. From: Bruce Evans <bde@zeta.org.au> To: Hal Burch <hburch@lumeta.com> Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/47168: st_*timespec tv_nsec zero on file creation Date: Sat, 18 Jan 2003 10:28:02 +1100 (EST) On Fri, 17 Jan 2003, Hal Burch wrote: > >Synopsis: st_*timespec tv_nsec zero on file creation > ... > >Fix: > I'm not familiar enough with the kernel tree to figure out where this > system times are being set. This may also be expected behavior. This is the expected behaviour. ffs timestamps always have a zero tv_nsec unless you use a nonstandard setting of the vfs.timestamp_precision to get a higher precision. Caveats: - the sysctl is supposed to affect all filesystems. - some filesystems can't support nsec resolution. - some filesystems that could support it don't. - copying and archiving utilities can't support full nsec resolution, since there is no syscall to set it. utimes() sets times in usec. - some copying and archiving utilities that could support usec resolution don't. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200301172330.h0HNU2Sj022732>