From: Arjan van de Ven <arjan@infradead.org>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [QUESTION] file access time in millisecond?
Date: Mon, 12 Feb 2007 09:01:00 +0100 [thread overview]
Message-ID: <1171267260.3081.32.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <b6a2187b0702112327t7294c221w460b3bd0f77d0e@mail.gmail.com>
On Mon, 2007-02-12 at 15:27 +0800, Jeff Chua wrote:
> Is it possible to get file access time in millisecond resolution?
>
> stat() returns time in seconds, but gettimeofday() can returns microseconds.
see the "utimes()" function
next prev parent reply other threads:[~2007-02-12 8:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-12 7:27 [QUESTION] file access time in millisecond? Jeff Chua
2007-02-12 8:01 ` Arjan van de Ven [this message]
2007-02-12 9:24 ` Jeff Chua
2007-02-12 9:02 ` Andi Kleen
2007-02-12 9:52 ` Jeff Chua
2007-02-12 9:56 ` Andi Kleen
2007-02-12 18:55 ` Jeff Chua
2007-02-12 10:01 ` Miquel van Smoorenburg
2007-02-12 18:58 ` Jeff Chua
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=1171267260.3081.32.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=jeff.chua.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).