From: Matthias Schniedermeyer <ms@citd.de>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Cesar Eduardo Barros <cesarb@nitnet.com.br>,
linux-kernel@vger.kernel.org, Alexander Viro <viro@math.psu.edu>
Subject: Re: [PATCH] O_NOATIME support
Date: Tue, 15 Jun 2004 21:32:05 +0200 [thread overview]
Message-ID: <20040615193205.GA25131@citd.de> (raw)
In-Reply-To: <orfz8wabng.fsf@free.redhat.lsd.ic.unicamp.br>
On Tue, Jun 15, 2004 at 04:01:23PM -0300, Alexandre Oliva wrote:
> On Jun 14, 2004, Cesar Eduardo Barros <cesarb@nitnet.com.br> wrote:
>
> > The atime was never intended as an auditing feature (if it were, utimes
> > and related functions would be root only).
>
> But utimes updates the inode modification time, so you can still tell
> something happened to the file.
No.
Bis denn
--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.
next prev parent reply other threads:[~2004-06-15 19:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-12 1:11 [PATCH] O_NOATIME support Cesar Eduardo Barros
2004-06-12 16:44 ` Bernd Eckenfels
2004-06-12 18:09 ` Chris Wedgwood
2004-06-12 18:22 ` Bernd Eckenfels
2004-06-14 9:55 ` Christoph Hellwig
2004-06-14 13:46 ` Cesar Eduardo Barros
2004-06-14 14:03 ` Christoph Hellwig
2004-06-14 19:25 ` Cesar Eduardo Barros
2004-06-14 16:57 ` David Lang
2004-06-14 19:34 ` Cesar Eduardo Barros
2004-06-14 15:38 ` Paul Jackson
2004-06-14 21:12 ` Alexandre Oliva
2004-06-14 21:58 ` Valdis.Kletnieks
2004-06-14 22:09 ` Matthias Schniedermeyer
2004-06-15 19:02 ` Alexandre Oliva
2004-06-16 1:49 ` Horst von Brand
2004-06-14 22:40 ` Cesar Eduardo Barros
2004-06-14 23:14 ` Bernd Eckenfels
2004-06-15 19:01 ` Alexandre Oliva
2004-06-15 19:32 ` Matthias Schniedermeyer [this message]
2004-06-15 22:03 ` Paul Jackson
2004-06-16 6:21 ` Matthias Schniedermeyer
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=20040615193205.GA25131@citd.de \
--to=ms@citd.de \
--cc=aoliva@redhat.com \
--cc=cesarb@nitnet.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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.