From: Robert Love <rml@novell.com>
To: Dale Blount <linux-kernel@dale.us>
Cc: John McCutchan <ttb@tentacle.dhs.org>, linux-kernel@vger.kernel.org
Subject: Re: [patch] inotify 0.22
Date: Mon, 04 Apr 2005 17:04:19 -0400 [thread overview]
Message-ID: <1112648659.7324.4.camel@betsy> (raw)
In-Reply-To: <1112647855.520.20.camel@dale.velocity.net>
On Mon, 2005-04-04 at 16:50 -0400, Dale Blount wrote:
Hi, Dale.
> Will inotify watch directories recursively? A quick browse through the
> source doesn't look like it, but I very well could be wrong. Last I
> checked, dnotify did not either. I am looking for a way to synchronize
> files in as-real-as-possible-time when they are modified.
No, inotify does not support watching directories recursively. I would
love to add it, but it would be a mess to do inside of the kernel.
Making it easy and efficient to watch a full tree, however, was a goal
of inotify. Beagle, a personal indexing infrastructure, watches the
user's entire home directory.
You could never do this in dnotify because you would run out of file
descriptors and pin every file.
In inotify, it is not hard to write a simple recursive loop to add a
watch to each directory starting at a given path. It can even be done
in an atomic fashion. See
http://mail.gnome.org/archives/dashboard-hackers/2004-October/msg00022.html
wherein I publish such an algorithm.
Hope this helps,
Robert Love
next prev parent reply other threads:[~2005-04-04 21:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 20:02 [patch] inotify 0.22 Robert Love
2005-04-04 20:18 ` [patch] inotify 0.22 for 2.6.12-rc1-mm4 Robert Love
2005-04-04 20:50 ` [patch] inotify 0.22 Dale Blount
2005-04-04 21:04 ` Robert Love [this message]
2005-04-04 22:21 ` John McCutchan
2005-04-05 9:26 ` Martin Schlemmer
2005-04-05 16:56 ` [patch] updated " Robert Love
2005-04-05 16:59 ` [patch] updated inotify 0.22 for 2.6-mm Robert Love
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=1112648659.7324.4.camel@betsy \
--to=rml@novell.com \
--cc=linux-kernel@dale.us \
--cc=linux-kernel@vger.kernel.org \
--cc=ttb@tentacle.dhs.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