From: Henrik Nordstrom <henrik@henriknordstrom.net>
To: Steve French <smfrench@gmail.com>
Cc: Sunil Mushran <sunil.mushran@oracle.com>,
jim owens <jowens@hp.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Andreas Dilger <adilger@sun.com>,
samba-technical <samba-technical@lists.samba.org>
Subject: Re: ext4 - getting at birth time (file create time) and getting/setting nanosecond time stamps and utime
Date: Wed, 21 Oct 2009 13:59:52 +0200 [thread overview]
Message-ID: <1256126392.493.640.camel@localhost.localdomain> (raw)
In-Reply-To: <524f69650910201411j3dc4897bic8a042cb17fcede8@mail.gmail.com>
tis 2009-10-20 klockan 16:11 -0500 skrev Steve French:
> "The function utime() allows specification of time stamps with a
> resolution of 1 second. ... The function utimes() is similar, but the
> times argument allows a reso lution of 1 microsecond for the
> timestamps. " 1 millisecond is not sufficient
But it isn't 1 millisecond, it's granulatity is 1 microsecond (1/1000
millisecond, or 1000 nanoseconds)
utime -> second (time_t), same granularity as old stat(), time() and
friends.
utimes -> microsecond (struct timeval) (1/1000000), same granularity as
gettimeofday() and friends.
utimen -> nanosecond (struct timespec) (1/1000000000), same granularity
as current stat(), clock_gettime() and friends.
Regards
Henrik
next prev parent reply other threads:[~2009-10-21 12:23 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-19 17:17 ext4 - getting at birth time (file create time) and getting/setting nanosecond time stamps and utime Steve French
2009-10-19 18:55 ` Andreas Dilger
2009-10-19 18:58 ` Jeremy Allison
2009-10-19 19:37 ` Steve French
2009-10-19 19:12 ` Zach Brown
2009-10-19 20:49 ` Jamie Lokier
2009-10-19 19:45 ` Steve French
2009-10-19 20:11 ` Andreas Dilger
2009-10-19 22:24 ` Steve French
2009-10-19 23:12 ` Andreas Dilger
2009-10-20 3:31 ` Steve French
2009-10-20 12:44 ` jim owens
2009-10-20 20:33 ` Andreas Dilger
2009-10-20 20:49 ` Steve French
2009-10-20 20:59 ` Sunil Mushran
2009-10-20 21:11 ` Steve French
2009-10-20 21:23 ` Sunil Mushran
2009-10-20 21:37 ` Steve French
2009-10-20 21:49 ` Sunil Mushran
2009-10-20 21:56 ` Steve French
2009-10-20 22:16 ` Sunil Mushran
2009-10-21 23:45 ` Mingming
2009-10-21 11:59 ` Henrik Nordstrom [this message]
2009-10-21 15:36 ` Steve French
2009-10-21 18:56 ` Brad Boyer
2009-10-21 23:03 ` Björn Jacke
2009-10-22 21:50 ` Steve French
2009-10-21 0:44 ` Andreas Dilger
2009-10-21 23:42 ` Mingming
2009-10-20 21:10 ` jim owens
2009-10-20 0:41 ` Mingming
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1256126392.493.640.camel@localhost.localdomain \
--to=henrik@henriknordstrom.net \
--cc=adilger@sun.com \
--cc=jowens@hp.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=smfrench@gmail.com \
--cc=sunil.mushran@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.