From: Juergen Hasch <lkml@elbonia.de>
To: rudi@lambda-computing.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: File change notification
Date: Thu, 1 Jan 2004 10:02:48 +0100 [thread overview]
Message-ID: <200401011002.48223.lkml@elbonia.de> (raw)
In-Reply-To: <3FF2FC85.5070906@lambda-computing.de>
Hi Rudi,
Am Mittwoch, 31. Dezember 2003 17:42 schrieb Rüdiger Klaehn:
>
> I wrote some experimental mechanism yesterday. Whenever a file is
> accessed or changed, I write all easily available information to a ring
> buffer which is presented to user space as a device. The information
> that is easily available is the inode number of the file or directory
> that has changed, the inode number of the directory in which the change
> took place, and in most cases the name of the dentry of the file that
> has changed.
I'm also interested in receiving file change notifications, especially
as I would like to get this working for Samba in a sane way.
However I don't think your approach would help me much. I simply don't
want to get every file being changed on the whole machine getting
reported to me.
I don't want to look up the inode every time, just to know if it belongs
to a directory I'm interested in.
Actually I *like* dnotify being local to a given directory and having
a fd so I know where the signal I receive belongs to.
So my selfish reasoning makes me want either
- dnotify being able to pass some more information if requested
(I actually tried this and it basically works, it is just too
crappy to post here)
or
- make poll()/epoll() work for file/directory access
So much for what I want :-)
...Juergen
next prev parent reply other threads:[~2004-01-01 9:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-31 16:42 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
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 [this message]
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=200401011002.48223.lkml@elbonia.de \
--to=lkml@elbonia.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome