From owner-freebsd-bugs  Fri Jan 17 15:30: 4 2003
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4B75B37B401
	for <freebsd-bugs@hub.freebsd.org>; Fri, 17 Jan 2003 15:30:03 -0800 (PST)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id EE0EC43F1E
	for <freebsd-bugs@hub.freebsd.org>; Fri, 17 Jan 2003 15:30:02 -0800 (PST)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
	by freefall.freebsd.org (8.12.6/8.12.6) with ESMTP id h0HNU2NS022733
	for <freebsd-bugs@freefall.freebsd.org>; Fri, 17 Jan 2003 15:30:02 -0800 (PST)
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.12.6/8.12.6/Submit) id h0HNU2Sj022732;
	Fri, 17 Jan 2003 15:30:02 -0800 (PST)
Date: Fri, 17 Jan 2003 15:30:02 -0800 (PST)
Message-Id: <200301172330.h0HNU2Sj022732@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
Cc: 
From: Bruce Evans <bde@zeta.org.au>
Subject: Re: kern/47168: st_*timespec tv_nsec zero on file creation
Reply-To: Bruce Evans <bde@zeta.org.au>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-bugs.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-bugs>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-bugs>
X-Loop: FreeBSD.org

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