[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20060806001105.GA20715@tuatara.stupidest.org>
Date: Sat, 5 Aug 2006 17:11:05 -0700
From: Chris Wedgwood <cw@...f.org>
To: dean gaudet <dean@...tic.org>
Cc: David Lang <dlang@...italinsight.com>,
Mark Fasheh <mark.fasheh@...cle.com>,
Arjan van de Ven <arjan@...ux.intel.com>,
Dave Kleikamp <shaggy@...tin.ibm.com>,
Christoph Hellwig <hch@....de>,
Valerie Henson <val_henson@...ux.intel.com>,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
Akkana Peck <akkana@...llowsky.com>,
Jesse Barnes <jesse.barnes@...el.com>, jsipek@...sunysb.edu,
Al Viro <viro@....linux.org.uk>
Subject: Re: [RFC] [PATCH] Relative lazy atime
On Sat, Aug 05, 2006 at 04:28:29PM -0700, dean gaudet wrote:
> i can't understand when atime is *ever* reliable... root doing
> backups with something like rsync will cause atimes to change.
well, rsync and friends could use O_NOATIME, but usually that isn't
worth the pain
> you can work around mutt's silly dependancy on atime by configuring
> it with --enable-buffy-size. so far mutt is the only program i've
> discovered which cares about atime.
i've seen other applications use it, but most are pretty tolerant
about it not working that way you might think it would
> also -- i wasn't aware that xfs tried to do a better job with atime
> updates... i'm not sure it's really that effective. i've got a
> busy shell/mail/web server
OT, you might fine ikeep helps a little
-
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/
Powered by blists - more mailing lists