From: Adrian Bunk <bunk@fs.tum.de>
To: Jeroen van Disseldorp <jdizzl@xs4all.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Detecting changes in a directory tree
Date: Fri, 17 Jan 2003 01:59:41 +0100 [thread overview]
Message-ID: <20030117005941.GT2333@fs.tum.de> (raw)
In-Reply-To: <200301161358.36497.jdizzl@xs4all.nl>
On Thu, Jan 16, 2003 at 01:58:36PM -0500, Jeroen van Disseldorp wrote:
> Hi,
Hi Jeroen,
> For an application I'm writing I need to know if files in a certain
> directory tree were modified and/or deleted by another process. I
> assume that that tree is mounted on the machine that my app is running
> on. The device it has mounted on can be a local HD, but it can also be
> hosted remotely and mounted over nfs.
>
> I know of FAM, but this is documented to only watch a directory 1 level
> deep, and I need the whole tree to be monitored. Does anyone know a
> solution for this? Does the kernel provide facilities for this?
>...
with a kernel >= 2.4.19 dnotify [1] might do what you want.
> Regards,
> Jeroen van Disseldorp mailto:jdizzl@xs4all.nl
cu
Adrian
[1] http://www.student.lu.se/~nbi98oli/dnotify.html
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2003-01-17 0:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 18:58 Detecting changes in a directory tree Jeroen van Disseldorp
2003-01-17 0:59 ` Adrian Bunk [this message]
2003-01-17 3:54 ` Jeroen van Disseldorp
-- strict thread matches above, loose matches on Subject: below --
2003-01-17 12:58 Jon Burgess
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=20030117005941.GT2333@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=jdizzl@xs4all.nl \
--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 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.