All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sunil Mushran <sunil.mushran@oracle.com>
To: Steve French <smfrench@gmail.com>
Cc: 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: Tue, 20 Oct 2009 15:16:13 -0700	[thread overview]
Message-ID: <4ADE36AD.6070904@oracle.com> (raw)
In-Reply-To: <524f69650910201456j58e1e3a5offc6d42902e39c07@mail.gmail.com>

Steve French wrote:
> On Tue, Oct 20, 2009 at 4:49 PM, Sunil Mushran <sunil.mushran@oracle.com> wrote:
>> Steve French wrote:
>>> On Tue, Oct 20, 2009 at 4:23 PM, Sunil Mushran <sunil.mushran@oracle.com>
>>> wrote:
>>>
>>>> If you are trying to update it, you can use utimensat(2).
>>>>
>>> Looks like that should work based on what I see in fs/utimes.c ... but
>>> I have heard from two that think it doesn't work, so time to test it
>>> ... (unfortunately
>>> the libc is not new enough on this system ... ugh).
>
> strace shows that touch on my ubuntu system still calls utimesat
> (touch --version displays v6.10 2008).   What version of touch are you
> running?
$ touch --version
touch (GNU coreutils) 6.10

I am running the same and it calls utimensat(). Time to look at the source.

  reply	other threads:[~2009-10-20 22:16 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 [this message]
2009-10-21 23:45                               ` Mingming
2009-10-21 11:59                     ` Henrik Nordstrom
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=4ADE36AD.6070904@oracle.com \
    --to=sunil.mushran@oracle.com \
    --cc=adilger@sun.com \
    --cc=jowens@hp.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=samba-technical@lists.samba.org \
    --cc=smfrench@gmail.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.