From 4a8e9bf14c33b356680298d29f7321d82d4fde5d Mon Sep 17 00:00:00 2001 From: Jim Meyering Date: Sat, 13 Nov 2010 08:02:02 +0100 Subject: stat: do not provide variable precision time stamps * src/stat.c: Don't include fstimeprec.c. (out_epoch_sec): Don't call fstimeprec. * NEWS: Update description. * doc/coreutils.texi: Likewise. --- doc/coreutils.texi | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'doc') diff --git a/doc/coreutils.texi b/doc/coreutils.texi index ce56b0e5e..6a4257f61 100644 --- a/doc/coreutils.texi +++ b/doc/coreutils.texi @@ -10718,10 +10718,10 @@ The valid @var{format} directives for files with @option{--format} and The @samp{%W}, @samp{%X}, @samp{%Y}, and @samp{%Z} formats accept a precision preceded by a period to specify the number of digits to -print after the decimal point. For example, @samp{%.9X} outputs the -last access time to nanosecond precision. If a period is given but no -precision, @command{stat} uses the estimated precision of the file -system. When discarding excess precision, time stamps are truncated +print after the decimal point. For example, @samp{%.3X} outputs the +last access time to millisecond precision. If a period is given but no +precision, @command{stat} uses 9 digits, so @samp{%.X} is equivalent to +@samp{%.9X} When discarding excess precision, time stamps are truncated toward minus infinity. @example @@ -10737,7 +10737,7 @@ precision: $ stat -c '[%.3Y]' /usr [1288929712.114] $ stat -c '[%.Y]' /usr - [1288929712.114951] + [1288929712.114951834] @end example The mount point printed by @samp{%m} is similar to that output -- cgit v1.2.3-70-g09d2