From: "Pádraig Brady" <P@draigBrady.com>
To: Erik Paulson <epaulson@cs.wisc.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: file changes without updating mtime
Date: Wed, 28 Jun 2006 14:38:14 +0100 [thread overview]
Message-ID: <44A28646.4020408@draigBrady.com> (raw)
In-Reply-To: <20060627181010.GE25040@cobalt.cs.wisc.edu>
Perhaps you could create a filesystem wrapper module
or Linux Security module or equivalent to intercept write/truncate etc.
to invalidate an extended attribute containing a checksum.
This extended attribute could be updated from userspace periodically,
and your userspace program would compare those checksums.
That would be generally useful. For example rsync could
use it to very quickly determine if it needed to sync file contents.
See also http://lkml.org/lkml/2006/5/17/138
Note also files mounted loopback and modified don't
have their mtime updated either. Perhaps the patch
referenced above addresses that?
Pádraig.
next prev parent reply other threads:[~2006-06-28 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 18:10 file changes without updating mtime Erik Paulson
2006-06-28 13:38 ` Pádraig Brady [this message]
2006-06-29 11:11 ` Pavel Machek
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=44A28646.4020408@draigBrady.com \
--to=p@draigbrady.com \
--cc=epaulson@cs.wisc.edu \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox