open(2) and O_NOATIME

[Xin LI]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jeremy Chadwick wrote:
> I've recently been reading about Linux's O_NOATIME flag to open(2), and
> I'm curious why we haven't implemented this.  There seem to be a lot of
> good reasons to implement such a thing.
> 
> Chances are it's due to lack of time/interest, which is expected, but I
> was wondering if there were other reasons.
> 
> I realise mount's noatime trumps this, but there are lots of scenarios
> where atime is desired as a default, but disabled in specific cases.

Em...  Allowing administrators to disable NOATIME would be a good thing,
but wouldn't allowing arbitrary program to decide whether atime should
be changed, be a serious security disaster?

Disclaimer: I'm not a big atime fan myself, actually I disable atime on
a lot of my servers for performance reasons :)

Cheers,
- --
Xin LI <delphij at delphij.net>	http://www.delphij.net/
FreeBSD - The Power to Serve!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAkkKaooACgkQi+vbBBjt66CImQCgj51GGHXFaGhsFk4fAAWhmfV5
+s4An2Hn2TCVhqXEpzEL3xNwxy6YE84M
=n7f/
-----END PGP SIGNATURE-----