Re: [PATCH] Make use of stat.ctime configurable
- From
Linus Torvalds <torvalds@linux-foundation.org>
- Date
- Jul 28, 2008, 16:09 UTC
- Message-ID
- <alpine.LFD.1.10.0807280906530.3486@nehalem.linux-foundation.org>
- In-Reply-To
- <20080728160446.GA16351@old.davidb.org>
On Mon, 28 Jul 2008, David Brown wrote:
Show 8 quoted lines
> On Mon, Jul 28, 2008 at 08:31:28AM +0200, Alex Riesen wrote: > > > because there are situations where it produces too much false > > positives. Like when file system crawlers keep changing it when > > scanning and using the ctime for marking scanned files. > > That's interesting, since most backup software uses the ctime to determine > file changes.
It really is just Beagle that is (was? I can dream) a piece of unbelievable crap.
Anybody who uses extended attributes as part of a indexing scheme is just insane. Modifying the file you are indexing is not just fundamentally wrong to begin with, but it will then also be incredibly inefficient to read those entries one at a time.
And no other sane model would ever touch 'ctime'.
Oh, well. Making ctime configurable is not wrong per se. But if it's Beagle that triggers this, the fix is sadly in the wrong place.
Linus