All of lore.kernel.org
 help / color / mirror / Atom feed
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 00:09:17 +0200	[thread overview]
Message-ID: <20040614220917.GA18941@citd.de> (raw)
In-Reply-To: <orpt81sv1g.fsf@free.redhat.lsd.ic.unicamp.br>

On Mon, Jun 14, 2004 at 06:12:59PM -0300, Alexandre Oliva wrote:
> On Jun 11, 2004, Cesar Eduardo Barros <cesarb@nitnet.com.br> wrote:
> 
> > int O_NOATIME  	Macro
> >   If this bit is set, read will not update the access time of the file.
> >   See File Times. This is used by programs that do backups, so that
> >   backing a file up does not count as reading it. Only the owner of the
> >   file or the superuser may use this bit.
> 
> IMHO it's a bad idea to enable the owner of the file to avoid changing
> the atime of their files.  I've heard more than once about the atime
> bit being used to as proof that a user had actually seen the contents
> of a file although s/he claimed s/he hadn't.  If it was root-only,
> atime could still be used for the same purpose, and would enable
> backups with tools that accessed the filesystem through the FS layer,
> as opposed to though the block layer, to keep such proof unchanged.

man mount
/noatime
-> You can disable updating the atime for the whole filesystem.

man utimes/touch -a
-> You can modify "at will" the atime & mtime of a file.


Or in other words, nothing you can't already manipulate at will today.



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.


  parent reply	other threads:[~2004-06-14 22:09 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 [this message]
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
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=20040614220917.GA18941@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.