All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Clark <michael@metaparadigm.com>
To: rudi@lambda-computing.de
Cc: ivern@acm.org, linux-kernel@vger.kernel.org
Subject: Re: File change notification
Date: Thu, 01 Jan 2004 09:28:08 +0800	[thread overview]
Message-ID: <3FF377A8.6040302@metaparadigm.com> (raw)
In-Reply-To: <3FF31A15.4070307@lambda-computing.de>

On 01/01/04 02:48, Rüdiger Klaehn wrote:
> Javier Fernandez-Ivern wrote:
> 
>> Rüdiger Klaehn wrote:
>>
>>> I have been wondering for some time why there is no decent file 
>>> change notification mechanism in linux. Is there some deep 
>>> philosophical reason for this, or is it just that nobody has found 
>>> the time to implement it? If it is the latter, I am willing to 
>>> implement it as long there is a chance to get this accepted into the 
>>> mainstream kernel.
>>
>>
>>
>> Well, there's fam.  But AFAIK that's all done in user space, and your 
>> approach would be significantly more efficient (as a matter of fact, 
>> fam could be modified to use your change device as a first level of 
>> notification.)
>>
> Fam is a user space library that has some nice features such as network 
> transparent change notification. It currently uses the dnotify mechanism 
> if the underlying kernel supports it, but as I mentioned the dnotify 
> mechanism requires an open file handle and works only for single 
> directories. If the underlying os does not support dnotify, fam resorts 
> to polling for file changes (yuk!).

Have you had a look at dazuko. It provides a consistent file access
notification mechanism (and also intervention for denying access) across
linux and freebsd. It is currently being used by various on-access
virus scanners. It is under active development and supports 2.6 (and 2.4)

http://www.dazuko.org/about.shtml

Seems like a good idea. I've always thought it would be nice to use
something like this to maintain a dynamic locatedb (among many other
potential uses).

~mc


  reply	other threads:[~2004-01-01  1:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-31 16:42 File change notification Rüdiger Klaehn
2003-12-31 18:20 ` Javier Fernandez-Ivern
2003-12-31 18:48   ` Rüdiger Klaehn
2004-01-01  1:28     ` Michael Clark [this message]
2004-01-01  1:58       ` Dave Jones
2004-01-01  2:18         ` Michael Clark
2004-01-01  2:30           ` Javier Fernandez-Ivern
2004-01-01 13:11       ` Rüdiger Klaehn
2003-12-31 20:49 ` Javier Fernandez-Ivern
2004-01-01  9:02 ` Juergen Hasch
2004-01-01 10:47 ` jw schultz
2004-01-01 12:44   ` Rüdiger Klaehn
2004-01-03  6:32     ` Jan Harkes
  -- strict thread matches above, loose matches on Subject: below --
2004-02-07  8:29 John Ogness
2004-02-07 14:01 ` Christoph Hellwig
     [not found] <18PG9-4og-27@gated-at.bofh.it>
     [not found] ` <18TgF-QJ-7@gated-at.bofh.it>
     [not found]   ` <18TJE-1qL-3@gated-at.bofh.it>
2003-12-31 19:30     ` René Scharfe
2002-11-01 21:31 file " Colin Burnett
2002-11-01 22:19 ` Chris Wright
2002-11-02 15:43   ` Jamie Lokier

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=3FF377A8.6040302@metaparadigm.com \
    --to=michael@metaparadigm.com \
    --cc=ivern@acm.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rudi@lambda-computing.de \
    /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.