From: christophe.hauser@supelec.fr (Christophe Hauser)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Tracing file size changes
Date: Mon, 15 Aug 2011 12:05:20 +1000 [thread overview]
Message-ID: <20110815020520.GG8498@localhost> (raw)
In-Reply-To: <20110813005840.GA23912@chris-laptop.a2hosting.com>
On Fri, Aug 12, 2011 at 08:58:41PM -0400, Chris wrote:
> > > Will Inotify help?
> > >
> > > http://en.wikipedia.org/wiki/Inotify
> > > http://www.kernel.org/doc/man-pages/online/pages/man7/inotify.7.html
> > >
> >
> > It is pretty much what I want to do, the problem with it is that it doesn't
> > appear to be recursive.
>
>
> I looked again tonight, and it appears that newer kernels with fanotify are
> able to do this. So the feature is available, just too new to be on my
> servers. Oh, well :P
>
> Thanks for the input. I will probably just end up doing what I can with
> ld_preload.
>
> Chris
Hi Chris,
I'm not sure whether that would help or not, but you could also do it in
kernel space using LSM (if you don't already use another LSM module).
With the file_security hook, you can track any changes on files and
store information in the extended attributes of the filesystem for
example. This might be a bit more flexible than a system wide
ld_preload.
My two cents.
--
Christophe
prev parent reply other threads:[~2011-08-15 2:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 23:06 Tracing file size changes Chris
2011-08-11 2:47 ` Adam Lee
2011-08-11 8:21 ` Vaughn Clinton
2011-08-12 15:29 ` Chris
2011-08-13 0:58 ` Chris
2011-08-15 2:05 ` Christophe Hauser [this message]
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=20110815020520.GG8498@localhost \
--to=christophe.hauser@supelec.fr \
--cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.