From: Ben Martin <monkeyiq@users.sourceforge.net>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: dnotify on a grand scale
Date: 17 Jun 2003 21:46:44 +1000 [thread overview]
Message-ID: <1055850404.8789.31.camel@sam> (raw)
Hi,
Firstly, could folks please CC me as I am not on the list.
Background: I work on the libferris project and recently have added
both fulltext and attribute indexing (think Extended attributes).
http://witme.sourceforge.net/libferris.web/
I am wishing to get a kind of extended output to what dnotify
currently gives which will allow be to keep a userland journal of all
file create, delete and modify actions. I am wanting this so that I can
run a cron job and only reindex the files that require it instead of
walking the filesystem and checking every file.
I'm quite happy to tinker away and add such an interface and do the
hacking myself. I've read over the current dnotify code a little while
back. What I'm wondering is what sort of interface for this journaling
that I am preposing would be most likely to get integrated into the
mainline tree? I am open to suggestions as to how folks think this is
best implemented.
I know C/C++ but don't know the kernel code much at all :(
Thanks.
reply other threads:[~2003-06-17 11:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1055850404.8789.31.camel@sam \
--to=monkeyiq@users.sourceforge.net \
--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