linux-kernel - Re: Noatime vs relatime

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070810151014.GT6372@mea-ext.zmailer.org>
Date:	Fri, 10 Aug 2007 18:10:14 +0300
From:	Matti Aarnio <matti.aarnio@...iler.org>
To:	Vlad <vladc6@...oo.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Noatime vs relatime

On Fri, Aug 10, 2007 at 07:26:46AM -0700, Vlad wrote:
... 
> "Warning: Atime will be disabled by default in future kernel versions,
> but you will still be able to turn it on when configuring the kernel."
> 
> This should give a heads-up to the 0.001% of people who still use
> atime so that they know to customize this option or start using modern
> file-monitoring techniques like inotify.

NO for two reasons:
  - atime semantics are just fine in server environments
  - inotify IS NOT scalable to millions of files, nor
    to situations where we want to check alteration weeks
    or months after the fact

In reality I would perhaps prefer mount-behaviour being altered
from 'by default do atime' to 'by default do noatime.

There MUST be an easy way to tell system that "yes, I want to track
last accesstime."


I did recently an embedded Linux PC system where the entire
system disk is a single Compact Flash -card.  I tried to play
with  noatime  option, but the system still kept writing things,
and thus I had to do full and somewhat drastic  read-only.


> Vlad

/Matti Aarnio
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/