public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jon Burgess" <Jon_Burgess@eur.3com.com>
To: Ben Breuninger <benb@uncontrolled.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: real-time file monitoring at the kernel level
Date: Wed, 11 Apr 2001 17:55:13 +0100	[thread overview]
Message-ID: <80256A2B.005D1824.00@notesmta.eur.3com.com> (raw)



 I have never tried it myself but it looks like it might do what you want:

http://oss.sgi.com/projects/fam/

fam and imon FAQ
===============

What is fam?
fam, the File Alteration Monitor, provides an API which applications can use to
be notified when specific files or directories are changed.

fam comes in two parts: fam, the daemon which listens for requests and delivers
notification, and libfam, a library which client applications can use to
communicate with fam.

If the monitored files are mounted from a remote host, the local fam will
attempt to contact fam on the remote host, and will pass the requests on to the
remote fam.

fam can also notify its clients when a file starts and stops execution. (The
IRIX Interactive Desktop uses this to change a program's icon while it's
running, for example.)

fam was originally written for IRIX in 1989 by Bruce Karsh, and was rewritten in
1995 by Bob Miller. This open-source release of fam builds and runs on both
Linux and IRIX, and is the same fam that will be included with IRIX 6.5.8.

What is imon?
imon, the Inode Monitor, is the part of the kernel that tells fam when files
have changed. When applications tell fam they're interested in files or
directories, fam passes that interest on to imon. When file operations are
performed on files monitored by imon, the kernel tells imon; imon tells fam, and
fam notifies the applications which are interested in the files.

imon was originally written for the IRIX kernel in 1989 by Wiltse Carpenter; the
Linux port was done by Roger Chickering. The Linux implementation in the imon
kernel patch is similar to the IRIX implementation in most ways, but it hooks
into the kernel filesystem code differently.



             reply	other threads:[~2001-04-11 16:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-11 16:55 Jon Burgess [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-11 11:19 real-time file monitoring at the kernel level Ben Breuninger
2001-04-12  4:45 ` Karim Yaghmour
2001-04-12 20:17   ` Ryan Butler

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=80256A2B.005D1824.00@notesmta.eur.3com.com \
    --to=jon_burgess@eur.3com.com \
    --cc=benb@uncontrolled.org \
    --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